diff options
| author | Laurențiu Nicola <lnicola@users.noreply.github.com> | 2025-09-29 04:29:28 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-29 04:29:28 +0000 |
| commit | 930451e17d47cc27b6c96cb358dfae2ed3a97c67 (patch) | |
| tree | 722e3fdf88fdae0903cd1ff43cfc801db18345d3 /tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr | |
| parent | c0e45c896823664c49d631e961208d640dc43c58 (diff) | |
| parent | 24f6f94c5ad90be5d1ced24d83b8485712bcc27a (diff) | |
| download | rust-930451e17d47cc27b6c96cb358dfae2ed3a97c67.tar.gz rust-930451e17d47cc27b6c96cb358dfae2ed3a97c67.zip | |
Merge pull request #20761 from rust-lang/rustc-pull
Rustc pull update
Diffstat (limited to 'tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr')
| -rw-r--r-- | tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr b/tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr index 36743aa8102..fefe7f46ead 100644 --- a/tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr +++ b/tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr @@ -5,7 +5,7 @@ LL | match 0usize { | ^^^^^^ pattern `usize::MAX..` not covered | = note: the matched value is of type `usize` - = note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively + = note: `usize::MAX` is not treated as exhaustive, so half-open ranges are necessary to match exhaustively help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown | LL ~ 0..=usize::MAX => {}, @@ -19,7 +19,7 @@ LL | match 0isize { | ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered | = note: the matched value is of type `isize` - = note: `isize` does not have fixed minimum and maximum values, so half-open ranges are necessary to match exhaustively + = note: `isize::MIN` and `isize::MAX` are not treated as exhaustive, so half-open ranges are necessary to match exhaustively help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms | LL ~ isize::MIN..=isize::MAX => {}, |