2022-09-02 22:01:35 -05:00
error[E0004]: non-exhaustive patterns: `T::A` not covered
2020-03-31 20:10:13 -05:00
--> $DIR/non-exhaustive-match.rs:7:11
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | match x { T::B => { } }
2022-09-02 22:01:35 -05:00
| ^ pattern `T::A` 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: `T` defined here
--> $DIR/non-exhaustive-match.rs:3:10
|
LL | enum T { A, B }
| - ^ not covered
2020-03-27 00:44:30 -05:00
= note: the matched value is of type `T`
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 or an explicit pattern as shown
2021-12-15 20:14:17 -06:00
|
2022-09-02 22:01:35 -05:00
LL | match x { T::B => { }, T::A => todo!() }
| +++++++++++++++++
2018-08-08 07:28:26 -05:00
error[E0004]: non-exhaustive patterns: `false` not covered
2020-03-31 20:10:13 -05:00
--> $DIR/non-exhaustive-match.rs:8:11
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | match true {
2018-08-08 07:28:26 -05:00
| ^^^^ pattern `false` 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 `bool`
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 or an explicit pattern as shown
2021-12-15 20:14:17 -06:00
|
2023-02-27 11:43:39 -06:00
LL ~ true => {},
2021-12-15 20:14:17 -06:00
LL + false => todo!()
|
2018-08-08 07:28:26 -05:00
error[E0004]: non-exhaustive patterns: `Some(_)` not covered
2020-03-31 20:10:13 -05:00
--> $DIR/non-exhaustive-match.rs:11:11
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | match Some(10) {
2018-08-08 07:28:26 -05:00
| ^^^^^^^^ pattern `Some(_)` not covered
2021-06-10 06:52:00 -05:00
|
2021-12-15 23:06:44 -06:00
note: `Option<i32>` defined here
--> $SRC_DIR/core/src/option.rs:LL:COL
2022-12-12 09:25:04 -06:00
::: $SRC_DIR/core/src/option.rs:LL:COL
|
= note: not covered
2020-09-02 02:40:56 -05:00
= note: the matched value is of type `Option<i32>`
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 or an explicit pattern as shown
2021-12-15 20:14:17 -06:00
|
2023-02-27 11:43:39 -06:00
LL ~ None => {},
2021-12-15 20:14:17 -06:00
LL + Some(_) => todo!()
|
2018-08-08 07:28:26 -05:00
2020-06-19 11:57:15 -05:00
error[E0004]: non-exhaustive patterns: `(_, _, i32::MIN..=3_i32)` and `(_, _, 5_i32..=i32::MAX)` not covered
2020-03-31 20:10:13 -05:00
--> $DIR/non-exhaustive-match.rs:14:11
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | match (2, 3, 4) {
2020-06-19 11:57:15 -05:00
| ^^^^^^^^^ patterns `(_, _, i32::MIN..=3_i32)` and `(_, _, 5_i32..=i32::MAX)` 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 `(i32, i32, i32)`
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
2021-12-15 20:14:17 -06:00
|
2023-02-27 11:43:39 -06:00
LL ~ (_, _, 4) => {},
2021-12-15 20:14:17 -06:00
LL + (_, _, i32::MIN..=3_i32) | (_, _, 5_i32..=i32::MAX) => todo!()
|
2018-08-08 07:28:26 -05:00
2022-09-02 22:01:35 -05:00
error[E0004]: non-exhaustive patterns: `(T::A, T::A)` and `(T::B, T::B)` not covered
2020-03-31 20:10:13 -05:00
--> $DIR/non-exhaustive-match.rs:18:11
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | match (T::A, T::A) {
2022-09-02 22:01:35 -05:00
| ^^^^^^^^^^^^ patterns `(T::A, T::A)` and `(T::B, T::B)` 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 `(T, T)`
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
2021-12-15 20:28:09 -06:00
|
2023-02-27 11:43:39 -06:00
LL ~ (T::B, T::A) => {},
2022-09-02 22:01:35 -05:00
LL + (T::A, T::A) | (T::B, T::B) => todo!()
2021-12-15 20:28:09 -06:00
|
2018-08-08 07:28:26 -05:00
2022-09-02 22:01:35 -05:00
error[E0004]: non-exhaustive patterns: `T::B` not covered
2020-03-31 20:10:13 -05:00
--> $DIR/non-exhaustive-match.rs:22:11
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | match T::A {
2022-09-02 22:01:35 -05:00
| ^^^^ pattern `T::B` 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: `T` defined here
--> $DIR/non-exhaustive-match.rs:3:13
|
LL | enum T { A, B }
| - ^ not covered
2020-03-27 00:44:30 -05:00
= note: the matched value is of type `T`
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 or an explicit pattern as shown
2021-12-15 20:14:17 -06:00
|
2023-02-27 11:43:39 -06:00
LL ~ T::A => {},
2022-09-02 22:01:35 -05:00
LL + T::B => todo!()
2021-12-15 20:14:17 -06:00
|
2018-08-08 07:28:26 -05:00
error[E0004]: non-exhaustive patterns: `[]` not covered
2020-03-31 20:10:13 -05:00
--> $DIR/non-exhaustive-match.rs:33:11
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | match *vec {
2018-08-08 07:28:26 -05:00
| ^^^^ pattern `[]` 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-09-02 02:40:56 -05:00
= note: the matched value is of type `[Option<isize>]`
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 or an explicit pattern as shown
2021-12-15 20:28:09 -06:00
|
2023-02-27 11:43:39 -06:00
LL ~ [None] => {},
2021-12-15 20:28:09 -06:00
LL + [] => todo!()
|
2018-08-08 07:28:26 -05:00
2019-11-03 17:11:04 -06:00
error[E0004]: non-exhaustive patterns: `[_, _, _, _, ..]` not covered
2020-03-31 20:10:13 -05:00
--> $DIR/non-exhaustive-match.rs:46:11
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | match *vec {
2019-11-03 17:11:04 -06:00
| ^^^^ pattern `[_, _, _, _, ..]` 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 `[f32]`
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 or an explicit pattern as shown
2021-12-15 20:28:09 -06:00
|
LL ~ [] => (),
LL + [_, _, _, _, ..] => todo!()
|
2018-08-08 07:28:26 -05:00
error: aborting due to 8 previous errors
For more information about this error, try `rustc --explain E0004`.
