rust/tests/ui/error-codes/E0004.stderr

error[E0004]: non-exhaustive patterns: `Terminator::HastaLaVistaBaby` not covered
  --> $DIR/E0004.rs:9:11
   |
LL |     match x {
   |           ^ pattern `Terminator::HastaLaVistaBaby` not covered
   |
note: `Terminator` defined here
  --> $DIR/E0004.rs:1:6
   |
LL | enum Terminator {
   |      ^^^^^^^^^^
LL |     HastaLaVistaBaby,
   |     ---------------- not covered
   = note: the matched value is of type `Terminator`
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 ~         Terminator::TalkToMyHand => {},
LL +         Terminator::HastaLaVistaBaby => todo!()
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0004`.
Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			error[E0004]: non-exhaustive patterns: `Terminator::HastaLaVistaBaby` not covered
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/E0004.rs:9:11`
Move some E0XXX to `ui` 2018-02-08 03:35:35 +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 \| match x {`
Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			\| ^ pattern `Terminator::HastaLaVistaBaby` not covered
Point at enum definition when match patterns are not exhaustive ``` error[E0004]: non-exhaustive patterns: type `X` is non-empty --> file.rs:9:11 \| 1 \| / enum X { 2 \| \| A, \| \| - variant not covered 3 \| \| B, \| \| - variant not covered 4 \| \| C, \| \| - variant not covered 5 \| \| } \| \|_- `X` defined here ... 9 \| match x { \| ^ \| = help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms error[E0004]: non-exhaustive patterns: `B` and `C` not covered --> file.rs:11:11 \| 1 \| / enum X { 2 \| \| A, 3 \| \| B, 4 \| \| C, \| \| - not covered 5 \| \| } \| \|_- `X` defined here ... 11 \| match x { \| ^ patterns `C` not covered ``` When a match expression doesn't have patterns covering every variant, point at the enum's definition span. On a best effort basis, point at the variant(s) that are missing. This does not handle the case when the missing pattern is due to a field's enum variants: ``` enum E1 { A, B, C, } enum E2 { A(E1), B, } fn foo() { match E2::A(E1::A) { E2::A(E1::B) => {} E2::B => {} } //~^ ERROR `E2::A(E1::A)` and `E2::A(E1::C)` not handled } ``` Unify look between match with no arms and match with some missing patterns. Fix #37518. 2019-02-10 13:12:00 +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: `Terminator` defined here
Tweak spans for "adt defined here" note 2023-10-29 05:50:59 +00:00			`--> $DIR/E0004.rs:1:6`
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 \| enum Terminator {`
Tweak spans for "adt defined here" note 2023-10-29 05:50:59 +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 \| HastaLaVistaBaby,`
Tweak spans for "adt defined here" note 2023-10-29 05:50:59 +00:00			`\| ---------------- not covered`
non-exhastive diagnostic: add note re. scrutinee type 2020-03-27 05:44:30 +00:00			= note: the matched value is of type `Terminator`
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 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-16 02:14:17 +00:00			`\|`
Perform match checking on THIR. 2023-02-27 17:43:39 +00:00			`LL ~ Terminator::TalkToMyHand => {},`
Include enum path in variant suggestion 2022-09-03 03:01:35 +00:00			`LL + Terminator::HastaLaVistaBaby => 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-16 02:14:17 +00:00			`\|`
Move some E0XXX to `ui` 2018-02-08 03:35:35 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move some E0XXX to `ui` 2018-02-08 03:35:35 +00:00
update tests 2018-03-03 14:59:40 +00:00			For more information about this error, try `rustc --explain E0004`.