2022-09-02 22:01:35 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `(Enum::B, _)`, `(Enum::C, _)`, `(Enum::D, _)` and 2 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/issue-35609.rs:10:11
|
2016-09-24 12:45:59 -05:00
|
|
|
|
|
2019-03-09 06:03:44 -06:00
|
|
|
LL | match (A, ()) {
|
2022-09-02 22:01:35 -05:00
|
|
|
| ^^^^^^^ patterns `(Enum::B, _)`, `(Enum::C, _)`, `(Enum::D, _)` and 2 more 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 07:12:00 -06:00
|
|
|
|
|
2020-03-27 00:44:30 -05:00
|
|
|
= note: the matched value is of type `(Enum, ())`
|
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, or multiple match arms
|
2021-12-15 20:14:17 -06:00
|
|
|
|
|
2023-02-27 11:43:39 -06:00
|
|
|
LL ~ (A, _) => {},
|
2021-12-15 20:14:17 -06:00
|
|
|
LL + _ => todo!()
|
|
|
|
|
|
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2022-09-02 22:01:35 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `(_, Enum::B)`, `(_, Enum::C)`, `(_, Enum::D)` and 2 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/issue-35609.rs:14:11
|
2016-09-24 12:45:59 -05:00
|
|
|
|
|
2019-03-09 06:03:44 -06:00
|
|
|
LL | match (A, A) {
|
2022-09-02 22:01:35 -05:00
|
|
|
| ^^^^^^ patterns `(_, Enum::B)`, `(_, Enum::C)`, `(_, Enum::D)` and 2 more 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 07:12:00 -06:00
|
|
|
|
|
2020-03-27 00:44:30 -05:00
|
|
|
= note: the matched value is of type `(Enum, Enum)`
|
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, or multiple match arms
|
2021-12-15 20:14:17 -06:00
|
|
|
|
|
2023-02-27 11:43:39 -06:00
|
|
|
LL ~ (_, A) => {},
|
2021-12-15 20:14:17 -06:00
|
|
|
LL + _ => todo!()
|
|
|
|
|
|
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2022-09-02 22:01:35 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `((Enum::B, _), _)`, `((Enum::C, _), _)`, `((Enum::D, _), _)` and 2 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/issue-35609.rs:18:11
|
2016-09-24 12:45:59 -05:00
|
|
|
|
|
2019-03-09 06:03:44 -06:00
|
|
|
LL | match ((A, ()), ()) {
|
2022-09-02 22:01:35 -05:00
|
|
|
| ^^^^^^^^^^^^^ patterns `((Enum::B, _), _)`, `((Enum::C, _), _)`, `((Enum::D, _), _)` and 2 more 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 07:12:00 -06:00
|
|
|
|
|
2020-03-27 00:44:30 -05:00
|
|
|
= note: the matched value is of type `((Enum, ()), ())`
|
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, or multiple match arms
|
2021-12-15 20:14:17 -06:00
|
|
|
|
|
2023-02-27 11:43:39 -06:00
|
|
|
LL ~ ((A, ()), _) => {},
|
2021-12-15 20:14:17 -06:00
|
|
|
LL + _ => todo!()
|
|
|
|
|
|
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2022-09-02 22:01:35 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `((Enum::B, _), _)`, `((Enum::C, _), _)`, `((Enum::D, _), _)` and 2 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/issue-35609.rs:22:11
|
2016-09-24 12:45:59 -05:00
|
|
|
|
|
2019-03-09 06:03:44 -06:00
|
|
|
LL | match ((A, ()), A) {
|
2022-09-02 22:01:35 -05:00
|
|
|
| ^^^^^^^^^^^^ patterns `((Enum::B, _), _)`, `((Enum::C, _), _)`, `((Enum::D, _), _)` and 2 more 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 07:12:00 -06:00
|
|
|
|
|
2020-03-27 00:44:30 -05:00
|
|
|
= note: the matched value is of type `((Enum, ()), Enum)`
|
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, or multiple match arms
|
2021-12-15 20:14:17 -06:00
|
|
|
|
|
2023-02-27 11:43:39 -06:00
|
|
|
LL ~ ((A, ()), _) => {},
|
2021-12-15 20:14:17 -06:00
|
|
|
LL + _ => todo!()
|
|
|
|
|
|
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2022-09-02 22:01:35 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `((Enum::B, _), _)`, `((Enum::C, _), _)`, `((Enum::D, _), _)` and 2 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/issue-35609.rs:26:11
|
2016-09-24 12:45:59 -05:00
|
|
|
|
|
2019-03-09 06:03:44 -06:00
|
|
|
LL | match ((A, ()), ()) {
|
2022-09-02 22:01:35 -05:00
|
|
|
| ^^^^^^^^^^^^^ patterns `((Enum::B, _), _)`, `((Enum::C, _), _)`, `((Enum::D, _), _)` and 2 more 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 07:12:00 -06:00
|
|
|
|
|
2020-03-27 00:44:30 -05:00
|
|
|
= note: the matched value is of type `((Enum, ()), ())`
|
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, or multiple match arms
|
2021-12-15 20:14:17 -06:00
|
|
|
|
|
2023-02-27 11:43:39 -06:00
|
|
|
LL ~ ((A, _), _) => {},
|
2021-12-15 20:14:17 -06:00
|
|
|
LL + _ => todo!()
|
|
|
|
|
|
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2022-09-02 22:01:35 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `S(Enum::B, _)`, `S(Enum::C, _)`, `S(Enum::D, _)` and 2 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/issue-35609.rs:31:11
|
2016-09-24 12:45:59 -05:00
|
|
|
|
|
2019-03-09 06:03:44 -06:00
|
|
|
LL | match S(A, ()) {
|
2022-09-02 22:01:35 -05:00
|
|
|
| ^^^^^^^^ patterns `S(Enum::B, _)`, `S(Enum::C, _)`, `S(Enum::D, _)` and 2 more 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 07:12:00 -06:00
|
|
|
|
|
2021-12-15 23:06:44 -06:00
|
|
|
note: `S` defined here
|
|
|
|
|
--> $DIR/issue-35609.rs:6:8
|
|
|
|
|
|
|
|
|
|
|
LL | struct S(Enum, ());
|
|
|
|
|
| ^
|
2020-03-27 00:44:30 -05:00
|
|
|
= note: the matched value is of type `S`
|
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, or multiple match arms
|
2021-12-15 20:14:17 -06:00
|
|
|
|
|
2023-02-27 11:43:39 -06:00
|
|
|
LL ~ S(A, _) => {},
|
2021-12-15 20:14:17 -06:00
|
|
|
LL + _ => todo!()
|
|
|
|
|
|
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2022-09-02 22:01:35 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `Sd { x: Enum::B, .. }`, `Sd { x: Enum::C, .. }`, `Sd { x: Enum::D, .. }` and 2 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/issue-35609.rs:35:11
|
2016-09-24 12:45:59 -05:00
|
|
|
|
|
2019-03-09 06:03:44 -06:00
|
|
|
LL | match (Sd { x: A, y: () }) {
|
2022-09-02 22:01:35 -05:00
|
|
|
| ^^^^^^^^^^^^^^^^^^^^ patterns `Sd { x: Enum::B, .. }`, `Sd { x: Enum::C, .. }`, `Sd { x: Enum::D, .. }` and 2 more 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 07:12:00 -06:00
|
|
|
|
|
2021-12-15 23:06:44 -06:00
|
|
|
note: `Sd` defined here
|
|
|
|
|
--> $DIR/issue-35609.rs:7:8
|
|
|
|
|
|
|
|
|
|
|
LL | struct Sd { x: Enum, y: () }
|
|
|
|
|
| ^^
|
2020-03-27 00:44:30 -05:00
|
|
|
= note: the matched value is of type `Sd`
|
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, or multiple match arms
|
2021-12-15 20:14:17 -06:00
|
|
|
|
|
2023-02-27 11:43:39 -06:00
|
|
|
LL ~ Sd { x: A, y: _ } => {},
|
2021-12-15 20:14:17 -06:00
|
|
|
LL + _ => todo!()
|
|
|
|
|
|
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2022-09-02 22:01:35 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `Some(Enum::B)`, `Some(Enum::C)`, `Some(Enum::D)` and 2 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/issue-35609.rs:39:11
|
2016-09-24 12:45:59 -05:00
|
|
|
|
|
2019-03-09 06:03:44 -06:00
|
|
|
LL | match Some(A) {
|
2022-09-02 22:01:35 -05:00
|
|
|
| ^^^^^^^ patterns `Some(Enum::B)`, `Some(Enum::C)`, `Some(Enum::D)` and 2 more 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 07:12:00 -06:00
|
|
|
|
|
2021-12-15 23:06:44 -06:00
|
|
|
note: `Option<Enum>` defined here
|
|
|
|
|
--> $SRC_DIR/core/src/option.rs:LL:COL
|
2020-09-02 02:40:56 -05:00
|
|
|
= note: the matched value is of type `Option<Enum>`
|
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, or multiple match arms
|
2021-12-15 20:28:09 -06:00
|
|
|
|
|
|
|
|
|
LL ~ None => (),
|
|
|
|
|
LL + _ => todo!()
|
|
|
|
|
|
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2017-07-02 05:49:30 -05:00
|
|
|
error: aborting due to 8 previous errors
|
2016-09-24 12:45:59 -05:00
|
|
|
|
2018-03-03 08:59:40 -06:00
|
|
|
For more information about this error, try `rustc --explain E0004`.
|
