rust/tests/ui/rfcs/rfc-2008-non-exhaustive/enum_same_crate_empty_match.stderr

error: unreachable pattern
  --> $DIR/enum_same_crate_empty_match.rs:28:9
   |
LL |         _ => {}
   |         ^------
   |         |
   |         matches no values because `EmptyNonExhaustiveEnum` is uninhabited
   |         help: remove the match arm
   |
   = note: to learn more about uninhabited types, see https://doc.rust-lang.org/nomicon/exotic-sizes.html#empty-types
note: the lint level is defined here
  --> $DIR/enum_same_crate_empty_match.rs:1:9
   |
LL | #![deny(unreachable_patterns)]
   |         ^^^^^^^^^^^^^^^^^^^^

error[E0004]: non-exhaustive patterns: `NonExhaustiveEnum::Unit`, `NonExhaustiveEnum::Tuple(_)` and `NonExhaustiveEnum::Struct { .. }` not covered
  --> $DIR/enum_same_crate_empty_match.rs:33:11
   |
LL |     match NonExhaustiveEnum::Unit {}
   |           ^^^^^^^^^^^^^^^^^^^^^^^ patterns `NonExhaustiveEnum::Unit`, `NonExhaustiveEnum::Tuple(_)` and `NonExhaustiveEnum::Struct { .. }` not covered
   |
note: `NonExhaustiveEnum` defined here
  --> $DIR/enum_same_crate_empty_match.rs:4:10
   |
LL | pub enum NonExhaustiveEnum {
   |          ^^^^^^^^^^^^^^^^^
LL |     Unit,
   |     ---- not covered
LL |
LL |     Tuple(u32),
   |     ----- not covered
LL |
LL |     Struct { field: u32 }
   |     ------ not covered
   = note: the matched value is of type `NonExhaustiveEnum`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
   |
LL ~     match NonExhaustiveEnum::Unit {
LL +         NonExhaustiveEnum::Unit | NonExhaustiveEnum::Tuple(_) | NonExhaustiveEnum::Struct { .. } => todo!(),
LL ~     }
   |

error[E0004]: non-exhaustive patterns: `NormalEnum::Unit`, `NormalEnum::Tuple(_)` and `NormalEnum::Struct { .. }` not covered
  --> $DIR/enum_same_crate_empty_match.rs:35:11
   |
LL |     match NormalEnum::Unit {}
   |           ^^^^^^^^^^^^^^^^ patterns `NormalEnum::Unit`, `NormalEnum::Tuple(_)` and `NormalEnum::Struct { .. }` not covered
   |
note: `NormalEnum` defined here
  --> $DIR/enum_same_crate_empty_match.rs:13:10
   |
LL | pub enum NormalEnum {
   |          ^^^^^^^^^^
LL |     Unit,
   |     ---- not covered
LL |
LL |     Tuple(u32),
   |     ----- not covered
LL |
LL |     Struct { field: u32 }
   |     ------ not covered
   = note: the matched value is of type `NormalEnum`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms
   |
LL ~     match NormalEnum::Unit {
LL +         NormalEnum::Unit | NormalEnum::Tuple(_) | NormalEnum::Struct { .. } => todo!(),
LL ~     }
   |

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0004`.
Handle empty matches cleanly 2020-11-12 17:28:55 +00:00			`error: unreachable pattern`
			`--> $DIR/enum_same_crate_empty_match.rs:28:9`
			`\|`
Apply suggestions from code review Co-authored-by: varkor <github@varkor.com> 2020-11-13 23:18:55 +00:00			`LL \| _ => {}`
Add a machine-applicable suggestion to "unreachable pattern" 2024-08-19 21:33:48 +02:00			`\| ^------`
			`\| \|`
			\| matches no values because `EmptyNonExhaustiveEnum` is uninhabited
			`\| help: remove the match arm`
Handle empty matches cleanly 2020-11-12 17:28:55 +00:00			`\|`
Add a note with a link to explain empty types 2024-08-19 21:08:18 +02:00			`= note: to learn more about uninhabited types, see https://doc.rust-lang.org/nomicon/exotic-sizes.html#empty-types`
Handle empty matches cleanly 2020-11-12 17:28:55 +00:00			`note: the lint level is defined here`
			`--> $DIR/enum_same_crate_empty_match.rs:1:9`
			`\|`
			`LL \| #![deny(unreachable_patterns)]`
			`\| ^^^^^^^^^^^^^^^^^^^^`

Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			error[E0004]: non-exhaustive patterns: `NonExhaustiveEnum::Unit`, `NonExhaustiveEnum::Tuple(_)` and `NonExhaustiveEnum::Struct { .. }` not covered
Add tests 2019-11-30 15:51:26 +00:00			`--> $DIR/enum_same_crate_empty_match.rs:33:11`
			`\|`
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-16 05:06:44 +00:00			`LL \| match NonExhaustiveEnum::Unit {}`
Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			\| ^^^^^^^^^^^^^^^^^^^^^^^ patterns `NonExhaustiveEnum::Unit`, `NonExhaustiveEnum::Tuple(_)` and `NonExhaustiveEnum::Struct { .. }` not covered
Add tests 2019-11-30 15:51:26 +00: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-16 05:06:44 +00:00			note: `NonExhaustiveEnum` defined here
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01:00			`--> $DIR/enum_same_crate_empty_match.rs:4:10`
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-16 05:06:44 +00:00			`\|`
			`LL \| pub enum NonExhaustiveEnum {`
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01: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-16 05:06:44 +00:00			`LL \| Unit,`
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01:00			`\| ---- not covered`
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-16 05:06:44 +00:00			`LL \|`
			`LL \| Tuple(u32),`
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01:00			`\| ----- not covered`
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-16 05:06:44 +00:00			`LL \|`
			`LL \| Struct { field: u32 }`
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01:00			`\| ------ not covered`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 06:44:30 +01:00			= note: the matched value is of type `NonExhaustiveEnum`
Change wording of suggestion to add missing `match` arm 2021-12-16 22:46:13 +00:00			`help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms`
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-16 02:05:58 +00:00			`\|`
			`LL ~ match NonExhaustiveEnum::Unit {`
Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			`LL + NonExhaustiveEnum::Unit \| NonExhaustiveEnum::Tuple(_) \| NonExhaustiveEnum::Struct { .. } => todo!(),`
Trim suggestion part before generating highlights 2025-02-21 00:29:56 +00:00			`LL ~ }`
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-16 02:05:58 +00:00			`\|`
Add tests 2019-11-30 15:51:26 +00:00
Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			error[E0004]: non-exhaustive patterns: `NormalEnum::Unit`, `NormalEnum::Tuple(_)` and `NormalEnum::Struct { .. }` not covered
Add tests 2019-11-30 15:51:26 +00:00			`--> $DIR/enum_same_crate_empty_match.rs:35:11`
			`\|`
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-16 05:06:44 +00:00			`LL \| match NormalEnum::Unit {}`
Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			\| ^^^^^^^^^^^^^^^^ patterns `NormalEnum::Unit`, `NormalEnum::Tuple(_)` and `NormalEnum::Struct { .. }` not covered
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-16 05:06:44 +00:00			`\|`
			note: `NormalEnum` defined here
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01:00			`--> $DIR/enum_same_crate_empty_match.rs:13:10`
Add tests 2019-11-30 15:51:26 +00: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-16 05:06:44 +00:00			`LL \| pub enum NormalEnum {`
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01: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-16 05:06:44 +00:00			`LL \| Unit,`
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01:00			`\| ---- not covered`
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-16 05:06:44 +00:00			`LL \|`
			`LL \| Tuple(u32),`
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01:00			`\| ----- not covered`
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-16 05:06:44 +00:00			`LL \|`
			`LL \| Struct { field: u32 }`
Tweak spans for "adt defined here" note 2023-10-29 06:50:59 +01:00			`\| ------ not covered`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 06:44:30 +01:00			= note: the matched value is of type `NormalEnum`
Change wording of suggestion to add missing `match` arm 2021-12-16 22:46:13 +00:00			`help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match arm with multiple or-patterns as shown, or multiple match arms`
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-16 02:05:58 +00:00			`\|`
			`LL ~ match NormalEnum::Unit {`
Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			`LL + NormalEnum::Unit \| NormalEnum::Tuple(_) \| NormalEnum::Struct { .. } => todo!(),`
Trim suggestion part before generating highlights 2025-02-21 00:29:56 +00:00			`LL ~ }`
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-16 02:05:58 +00:00			`\|`
Add tests 2019-11-30 15:51:26 +00:00
Handle empty matches cleanly 2020-11-12 17:28:55 +00:00			`error: aborting due to 3 previous errors`
Add tests 2019-11-30 15:51:26 +00:00
			For more information about this error, try `rustc --explain E0004`.