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

error[E0004]: non-exhaustive patterns: `Foo::A(false)`, `Foo::B(false)` and `Foo::C(false)` not covered
  --> $DIR/issue-56379.rs:8:11
   |
LL |     match Foo::A(true) {
   |           ^^^^^^^^^^^^ patterns `Foo::A(false)`, `Foo::B(false)` and `Foo::C(false)` not covered
   |
note: `Foo` defined here
  --> $DIR/issue-56379.rs:2:5
   |
LL | enum Foo {
   |      ---
LL |     A(bool),
   |     ^ not covered
LL |     B(bool),
   |     ^ not covered
LL |     C(bool),
   |     ^ not covered
   = 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, a match arm with multiple or-patterns as shown, or multiple match arms
   |
LL ~         Foo::C(true) => {},
LL +         Foo::A(false) | Foo::B(false) | Foo::C(false) => 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: `Foo::A(false)`, `Foo::B(false)` and `Foo::C(false)` not covered
Add tests 2020-12-16 18:42:49 -06:00			`--> $DIR/issue-56379.rs:8: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-15 23:06:44 -06:00			`LL \| match Foo::A(true) {`
Include enum path in variant suggestion 2022-09-02 22:01:35 -05:00			\| ^^^^^^^^^^^^ patterns `Foo::A(false)`, `Foo::B(false)` and `Foo::C(false)` not covered
Add tests 2020-12-16 18:42:49 -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/issue-56379.rs:2:5`
			`\|`
			`LL \| enum Foo {`
			`\| ---`
			`LL \| A(bool),`
			`\| ^ not covered`
			`LL \| B(bool),`
			`\| ^ not covered`
			`LL \| C(bool),`
			`\| ^ not covered`
Add tests 2020-12-16 18:42:49 -06: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, a match arm with multiple or-patterns as shown, or multiple match arms`
When finding a match expr with multiple arms that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} Some(1) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} Some(1) => {} None \| Some(_) => todo!(), } ``` 2021-12-15 20:28:09 -06:00			`\|`
Perform match checking on THIR. 2023-02-27 11:43:39 -06:00			`LL ~ Foo::C(true) => {},`
Include enum path in variant suggestion 2022-09-02 22:01:35 -05:00			`LL + Foo::A(false) \| Foo::B(false) \| Foo::C(false) => todo!()`
When finding a match expr with multiple arms that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} Some(1) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} Some(1) => {} None \| Some(_) => todo!(), } ``` 2021-12-15 20:28:09 -06:00			`\|`
Add tests 2020-12-16 18:42:49 -06:00
			`error: aborting due to previous error`

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