rust/tests/ui/pattern/usefulness/integer-ranges/precise_pointer_matching-message.stderr

error[E0004]: non-exhaustive patterns: `usize::MAX..` not covered
  --> $DIR/precise_pointer_matching-message.rs:3:11
   |
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
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 => {},
LL +         usize::MAX.. => todo!()
   |

error[E0004]: non-exhaustive patterns: `..isize::MIN` and `isize::MAX..` not covered
  --> $DIR/precise_pointer_matching-message.rs:11:11
   |
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
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 => {},
LL +         ..isize::MIN | isize::MAX.. => todo!()
   |

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0004`.
Match usize/isize exhaustively 2023-10-12 22:20:06 +00:00			error[E0004]: non-exhaustive patterns: `usize::MAX..` not covered
Improve integer range tests 2020-11-20 19:03:56 +00:00			`--> $DIR/precise_pointer_matching-message.rs:3:11`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 17:37:52 +00:00			`\|`
			`LL \| match 0usize {`
Match usize/isize exhaustively 2023-10-12 22:20:06 +00:00			\| ^^^^^^ pattern `usize::MAX..` not covered
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 17:37:52 +00:00			`\|`
			= note: the matched value is of type `usize`
Match usize/isize exhaustively 2023-10-12 22:20:06 +00:00			= note: `usize` does not have a fixed maximum value, so half-open ranges are necessary to match exhaustively
Change wording of suggestion to add missing `match` arm 2021-12-16 22:46:13 +00:00			`help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown`
When finding a match expr with a single arm that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None \| Some(_) => todo!(), } ``` 2021-12-16 02:14:17 +00:00			`\|`
Perform match checking on THIR. 2023-02-27 17:43:39 +00:00			`LL ~ 0..=usize::MAX => {},`
Match usize/isize exhaustively 2023-10-12 22:20:06 +00:00			`LL + usize::MAX.. => todo!()`
When finding a match expr with a single arm that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None \| Some(_) => todo!(), } ``` 2021-12-16 02:14:17 +00:00			`\|`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 17:37:52 +00:00
Match usize/isize exhaustively 2023-10-12 22:20:06 +00:00			error[E0004]: non-exhaustive patterns: `..isize::MIN` and `isize::MAX..` not covered
Improve integer range tests 2020-11-20 19:03:56 +00:00			`--> $DIR/precise_pointer_matching-message.rs:11:11`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 17:37:52 +00:00			`\|`
			`LL \| match 0isize {`
Match usize/isize exhaustively 2023-10-12 22:20:06 +00:00			\| ^^^^^^ patterns `..isize::MIN` and `isize::MAX..` not covered
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 17:37:52 +00:00			`\|`
			= note: the matched value is of type `isize`
Match usize/isize exhaustively 2023-10-12 22:20:06 +00:00			= note: `isize` does not have fixed minimum and maximum values, 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`
When finding a match expr with a single arm that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None \| Some(_) => todo!(), } ``` 2021-12-16 02:14:17 +00:00			`\|`
Perform match checking on THIR. 2023-02-27 17:43:39 +00:00			`LL ~ isize::MIN..=isize::MAX => {},`
Match usize/isize exhaustively 2023-10-12 22:20:06 +00:00			`LL + ..isize::MIN \| isize::MAX.. => todo!()`
When finding a match expr with a single arm that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None \| Some(_) => todo!(), } ``` 2021-12-16 02:14:17 +00:00			`\|`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 17:37:52 +00:00
Improve integer range tests 2020-11-20 19:03:56 +00:00			`error: aborting due to 2 previous errors`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 17:37:52 +00:00
			For more information about this error, try `rustc --explain E0004`.