rust/tests/ui/pattern/usefulness/issue-50900.stderr

error[E0004]: non-exhaustive patterns: `Tag(Context::Exif, _)` not covered
  --> $DIR/issue-50900.rs:15:11
   |
LL |     match Tag::ExifIFDPointer {
   |           ^^^^^^^^^^^^^^^^^^^ pattern `Tag(Context::Exif, _)` not covered
   |
note: `Tag` defined here
  --> $DIR/issue-50900.rs:2:12
   |
LL | pub struct Tag(pub Context, pub u16);
   |            ^^^
   = note: the matched value is of type `Tag`
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 ~         Tag::ExifIFDPointer => {}
LL +         Tag(Context::Exif, _) => todo!()
   |

error: aborting due to previous error

For more information about this error, try `rustc --explain E0004`.
Include enum path in variant suggestion 2022-09-02 22:01:35 -05:00			error[E0004]: non-exhaustive patterns: `Tag(Context::Exif, _)` not covered
Add test for issue-50900 2019-07-28 02:26:01 -05:00			`--> $DIR/issue-50900.rs:15:11`
			`\|`
			`LL \| match Tag::ExifIFDPointer {`
Include enum path in variant suggestion 2022-09-02 22:01:35 -05:00			\| ^^^^^^^^^^^^^^^^^^^ pattern `Tag(Context::Exif, _)` not covered
Add test for issue-50900 2019-07-28 02:26:01 -05:00			`\|`
Point at uncovered variants in enum definition in `note` instead of a `span_label` This makes the order of the output always consistent: 1. Place of the `match` missing arms 2. The `enum` definition span 3. The structured suggestion to add a fallthrough arm 2021-12-15 23:06:44 -06:00			note: `Tag` defined here
			`--> $DIR/issue-50900.rs:2:12`
			`\|`
			`LL \| pub struct Tag(pub Context, pub u16);`
			`\| ^^^`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 00:44:30 -05:00			= note: the matched value is of type `Tag`
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			`\|`
			`LL ~ Tag::ExifIFDPointer => {}`
Include enum path in variant suggestion 2022-09-02 22:01:35 -05:00			`LL + Tag(Context::Exif, _) => 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-15 20:14:17 -06:00			`\|`
Add test for issue-50900 2019-07-28 02:26:01 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0004`.