rust/tests/ui/pattern/usefulness/always-inhabited-union-ref.stderr

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

error[E0004]: non-exhaustive patterns: type `Foo` is non-empty
  --> $DIR/always-inhabited-union-ref.rs:27:11
   |
LL |     match uninhab_union() {
   |           ^^^^^^^^^^^^^^^
   |
note: `Foo` defined here
  --> $DIR/always-inhabited-union-ref.rs:10:11
   |
LL | pub union Foo {
   |           ^^^
   = note: the matched value is of type `Foo`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern as shown
   |
LL ~     match uninhab_union() {
LL +         _ => todo!(),
LL +     }
   |

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0004`.
Update tests for erasing regions in typeck 2020-02-15 06:13:20 -06:00			error[E0004]: non-exhaustive patterns: type `&!` is non-empty
Clarify undecided semantics 2018-11-20 15:33:57 -06:00			`--> $DIR/always-inhabited-union-ref.rs:23:11`
Add a test for uninhabitedness changes 2018-11-20 14:44:39 -06:00			`\|`
			`LL \| match uninhab_ref() {`
			`\| ^^^^^^^^^^^^^`
			`\|`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 00:44:30 -05:00			= note: the matched value is of type `&!`
Add note to non-exhaustive match on reference to empty Rust prints "type `&A` is non-empty" even is A is empty. This is the intended behavior, but can be confusing. This commit adds a note to non-exhaustive pattern errors if they are a reference to something uninhabited. I did not add tests to check that the note is not shown for non-references or inhabited references, because this is already done in other tests. Maybe the added test is superfluous, because `always-inhabited-union-ref` already checks for this case. This does not handle &&Void or &&&void etc. I could add those as special cases as well and ignore people who need quadruple references. Fixes #78123 2021-01-03 07:13:33 -06:00			`= note: references are always considered inhabited`
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 uninhab_ref() {`
			`LL + _ => todo!(),`
			`LL + }`
			`\|`
Add a test for uninhabitedness changes 2018-11-20 14:44:39 -06:00
Only warn about missing patterns in the case of an enum 2019-12-03 08:08:14 -06:00			error[E0004]: non-exhaustive patterns: type `Foo` is non-empty
Clarify undecided semantics 2018-11-20 15:33:57 -06:00			`--> $DIR/always-inhabited-union-ref.rs:27:11`
Add a test for uninhabitedness changes 2018-11-20 14:44:39 -06: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			`LL \| match uninhab_union() {`
			`\| ^^^^^^^^^^^^^^^`
Add a test for uninhabitedness changes 2018-11-20 14:44:39 -06: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: `Foo` defined here
			`--> $DIR/always-inhabited-union-ref.rs:10:11`
			`\|`
			`LL \| pub union Foo {`
			`\| ^^^`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 00:44:30 -05:00			= note: the matched value is of type `Foo`
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 uninhab_union() {`
			`LL + _ => todo!(),`
			`LL + }`
			`\|`
Add a test for uninhabitedness changes 2018-11-20 14:44:39 -06:00
			`error: aborting due to 2 previous errors`

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