diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-02-08 09:06:35 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-08 09:06:35 +0100 |
| commit | 5157190008f4e285e825b1eeefa0e9b171d1f5e9 (patch) | |
| tree | 246f5912267ada7f62b55287c54a9a3eae01c4c9 /compiler/rustc_hir_analysis/src/structured_errors.rs | |
| parent | fec32358b559eee00e5ce41ca16b6bf5ba6764f8 (diff) | |
| parent | 9dca6be7b83f4816f67ebaa11008348ce022eb60 (diff) | |
| download | rust-5157190008f4e285e825b1eeefa0e9b171d1f5e9.tar.gz rust-5157190008f4e285e825b1eeefa0e9b171d1f5e9.zip | |
Rollup merge of #120727 - Nadrieril:tweak-int-reporting, r=compiler-errors
exhaustiveness: Prefer "`0..MAX` not covered" to "`_` not covered" There was an exception when reporting integer ranges as missing, it's been there for as long as I can remember. This PR removes it. I think it's nicer to report "`0..MAX` not covered" than "`_` not covered". This also makes it consistent with enums, where we report individual enum variants in this case (as showcased in the rest of the `empty-match.rs` test). r? ``@estebank``
Diffstat (limited to 'compiler/rustc_hir_analysis/src/structured_errors.rs')
0 files changed, 0 insertions, 0 deletions