diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-05-01 01:09:49 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-01 01:09:49 +0200 |
| commit | 7b488f4598ecaa6d78625289831e012d73b86231 (patch) | |
| tree | 379f6fe9954c29f5adbe79f6017250dfb9dea110 /tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs | |
| parent | 124aad337fa728af3c2a3bad820f769d54b1f432 (diff) | |
| parent | f93f6c5cc5dcfe479f627afad9609a785edef860 (diff) | |
| download | rust-7b488f4598ecaa6d78625289831e012d73b86231.tar.gz | |
Rollup merge of #111033 - Nadrieril:Nadrieril-triagebot, r=compiler-errors
Ping Nadrieril when changing exhaustiveness checking
Hi!
I don't know what the procedure is but I'd quite like to be pinged when people try to change the exhaustiveness code. It's a tricky piece of code and I'm the de facto expert on it; I'd like to be available to provide feedback to contributors who wish to change it. I occasionally look through the git history and open PRs but a triagebot ping would be much more convenient.
The message says "might have" because `check_match.rs` contains a little bit of exhaustiveness logic and a lot of other match-related checks, so this ping will have false positives.
Diffstat (limited to 'tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs')
0 files changed, 0 insertions, 0 deletions