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

error[E0004]: non-exhaustive patterns: `_` not covered
  --> $DIR/precise_pointer_matching-message.rs:3:11
   |
LL |     match 0usize {
   |           ^^^^^^ pattern `_` not covered
   |
   = note: the matched value is of type `usize`
   = note: `usize` does not have a fixed maximum value, so a wildcard `_` is necessary to match exhaustively
   = help: add `#![feature(precise_pointer_size_matching)]` to the crate attributes to enable precise `usize` matching
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 +         _ => todo!()
   |

error[E0004]: non-exhaustive patterns: `_` not covered
  --> $DIR/precise_pointer_matching-message.rs:11:11
   |
LL |     match 0isize {
   |           ^^^^^^ pattern `_` not covered
   |
   = note: the matched value is of type `isize`
   = note: `isize` does not have a fixed maximum value, so a wildcard `_` is necessary to match exhaustively
   = help: add `#![feature(precise_pointer_size_matching)]` to the crate attributes to enable precise `isize` matching
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 ~         isize::MIN..=isize::MAX => {},
LL +         _ => todo!()
   |

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0004`.
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 12:37:52 -05:00			error[E0004]: non-exhaustive patterns: `_` not covered
Improve integer range tests 2020-11-20 13:03:56 -06:00			`--> $DIR/precise_pointer_matching-message.rs:3:11`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 12:37:52 -05:00			`\|`
			`LL \| match 0usize {`
			\| ^^^^^^ pattern `_` not covered
			`\|`
			= note: the matched value is of type `usize`
Address code reviews 2020-07-04 13:40:59 -05:00			= note: `usize` does not have a fixed maximum value, so a wildcard `_` is necessary to match exhaustively
			= help: add `#![feature(precise_pointer_size_matching)]` to the crate attributes to enable precise `usize` matching
Change wording of suggestion to add missing `match` arm 2021-12-16 16:46:13 -06: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-15 20:14:17 -06:00			`\|`
Perform match checking on THIR. 2023-02-27 11:43:39 -06:00			`LL ~ 0..=usize::MAX => {},`
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-15 20:14:17 -06:00			`LL + _ => todo!()`
			`\|`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 12:37:52 -05:00
			error[E0004]: non-exhaustive patterns: `_` not covered
Improve integer range tests 2020-11-20 13:03:56 -06:00			`--> $DIR/precise_pointer_matching-message.rs:11:11`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 12:37:52 -05:00			`\|`
			`LL \| match 0isize {`
			\| ^^^^^^ pattern `_` not covered
			`\|`
			= note: the matched value is of type `isize`
Address code reviews 2020-07-04 13:40:59 -05:00			= note: `isize` does not have a fixed maximum value, so a wildcard `_` is necessary to match exhaustively
			= help: add `#![feature(precise_pointer_size_matching)]` to the crate attributes to enable precise `isize` matching
Change wording of suggestion to add missing `match` arm 2021-12-16 16:46:13 -06: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-15 20:14:17 -06:00			`\|`
Perform match checking on THIR. 2023-02-27 11:43:39 -06:00			`LL ~ isize::MIN..=isize::MAX => {},`
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-15 20:14:17 -06:00			`LL + _ => todo!()`
			`\|`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 12:37:52 -05:00
Improve integer range tests 2020-11-20 13:03:56 -06:00			`error: aborting due to 2 previous errors`
Explain exhaustive matching on {usize,isize} maximum values 2020-07-01 12:37:52 -05:00
			For more information about this error, try `rustc --explain E0004`.