rust/tests/ui/pattern/usefulness/issue-3096-1.stderr

error[E0004]: non-exhaustive patterns: type `()` is non-empty
  --> $DIR/issue-3096-1.rs:2:11
   |
LL |     match () { }
   |           ^^
   |
   = note: the matched value is of type `()`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern as shown
   |
LL ~     match () {
LL +         _ => todo!(),
LL ~     }
   |

error: aborting due to previous error

For more information about this error, try `rustc --explain E0004`.
Enclose type in backticks for "non-exhaustive patterns" error This makes the error style consistent with the convention in error messages. 2018-11-20 15:48:13 -06:00			error[E0004]: non-exhaustive patterns: type `()` is non-empty
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-3096-1.rs:2:11`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| match () { }`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\| ^^`
			`\|`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 00:44:30 -05:00			= note: the matched value is of type `()`
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 as shown`
When encountering a match expr with no arms, suggest it Given ```rust match Some(42) {} ``` suggest ```rust match Some(42) { None \| Some(_) => todo!(), } ``` 2021-12-15 20:05:58 -06:00			`\|`
			`LL ~ match () {`
			`LL + _ => todo!(),`
			`LL ~ }`
			`\|`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to previous error`

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