rust/tests/ui/or-patterns/exhaustiveness-non-exhaustive.stderr

error[E0004]: non-exhaustive patterns: `(2_u8..=u8::MAX, _)` not covered
  --> $DIR/exhaustiveness-non-exhaustive.rs:5:11
   |
LL |     match (0u8, 0u8) {
   |           ^^^^^^^^^^ pattern `(2_u8..=u8::MAX, _)` not covered
   |
   = note: the matched value is of type `(u8, u8)`
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 | 1, 2 | 3) => {},
LL +         (2_u8..=u8::MAX, _) => todo!()
   |

error[E0004]: non-exhaustive patterns: `((4_u8..=u8::MAX))` not covered
  --> $DIR/exhaustiveness-non-exhaustive.rs:9:11
   |
LL |     match ((0u8,),) {
   |           ^^^^^^^^^ pattern `((4_u8..=u8::MAX))` not covered
   |
   = note: the matched value is of type `((u8,),)`
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 | 1,) | (2 | 3,),) => {},
LL +         ((4_u8..=u8::MAX)) => todo!()
   |

error[E0004]: non-exhaustive patterns: `(Some(2_u8..=u8::MAX))` not covered
  --> $DIR/exhaustiveness-non-exhaustive.rs:13:11
   |
LL |     match (Some(0u8),) {
   |           ^^^^^^^^^^^^ pattern `(Some(2_u8..=u8::MAX))` not covered
   |
   = note: the matched value is of type `(Option<u8>,)`
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 ~         (None | Some(0 | 1),) => {},
LL +         (Some(2_u8..=u8::MAX)) => todo!()
   |

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0004`.
Show the values and computation that would overflow a const evaluation or propagation 2020-06-19 11:57:15 -05:00			error[E0004]: non-exhaustive patterns: `(2_u8..=u8::MAX, _)` not covered
update tests 2020-11-21 16:05:17 -06:00			`--> $DIR/exhaustiveness-non-exhaustive.rs:5:11`
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00			`\|`
			`LL \| match (0u8, 0u8) {`
Show the values and computation that would overflow a const evaluation or propagation 2020-06-19 11:57:15 -05:00			\| ^^^^^^^^^^ pattern `(2_u8..=u8::MAX, _)` not covered
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00			`\|`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 00:44:30 -05:00			= note: the matched value is of type `(u8, u8)`
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 \| 1, 2 \| 3) => {},`
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 + (2_u8..=u8::MAX, _) => todo!()`
			`\|`
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00
Show the values and computation that would overflow a const evaluation or propagation 2020-06-19 11:57:15 -05:00			error[E0004]: non-exhaustive patterns: `((4_u8..=u8::MAX))` not covered
update tests 2020-11-21 16:05:17 -06:00			`--> $DIR/exhaustiveness-non-exhaustive.rs:9:11`
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00			`\|`
			`LL \| match ((0u8,),) {`
Show the values and computation that would overflow a const evaluation or propagation 2020-06-19 11:57:15 -05:00			\| ^^^^^^^^^ pattern `((4_u8..=u8::MAX))` not covered
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00			`\|`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 00:44:30 -05:00			= note: the matched value is of type `((u8,),)`
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 \| 1,) \| (2 \| 3,),) => {},`
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 + ((4_u8..=u8::MAX)) => todo!()`
			`\|`
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00
Show the values and computation that would overflow a const evaluation or propagation 2020-06-19 11:57:15 -05:00			error[E0004]: non-exhaustive patterns: `(Some(2_u8..=u8::MAX))` not covered
update tests 2020-11-21 16:05:17 -06:00			`--> $DIR/exhaustiveness-non-exhaustive.rs:13:11`
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00			`\|`
			`LL \| match (Some(0u8),) {`
Show the values and computation that would overflow a const evaluation or propagation 2020-06-19 11:57:15 -05:00			\| ^^^^^^^^^^^^ pattern `(Some(2_u8..=u8::MAX))` not covered
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00			`\|`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			= note: the matched value is of type `(Option<u8>,)`
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 ~ (None \| Some(0 \| 1),) => {},`
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 + (Some(2_u8..=u8::MAX)) => todo!()`
			`\|`
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00
Update existing tests for or-patterns 2019-12-27 11:53:00 -06:00			`error: aborting due to 3 previous errors`
Move tests to ui, split them and add some 2019-11-26 08:53:54 -06:00
			For more information about this error, try `rustc --explain E0004`.