2018-08-08 07:28:26 -05:00
|
|
|
error[E0005]: refutable pattern in local binding: `T(_, _)` not covered
|
2019-12-11 08:51:28 -06:00
|
|
|
--> $DIR/empty-never-array.rs:10:9
|
2018-08-08 07:28:26 -05:00
|
|
|
|
|
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
|
|
|
LL | / enum Helper<T, U> {
|
|
|
|
|
LL | | T(T, [!; 0]),
|
2019-09-09 09:44:06 -05:00
|
|
|
| | - 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
|
|
|
LL | | #[allow(dead_code)]
|
|
|
|
|
LL | | U(U),
|
|
|
|
|
LL | | }
|
|
|
|
|
| |_- `Helper<T, U>` defined here
|
|
|
|
|
...
|
|
|
|
|
LL | let Helper::U(u) = Helper::T(t, []);
|
|
|
|
|
| ^^^^^^^^^^^^ pattern `T(_, _)` not covered
|
2019-10-09 14:25:48 -05:00
|
|
|
|
|
|
|
|
|
= note: `let` bindings require an "irrefutable pattern", like a `struct` or an `enum` with only one variant
|
|
|
|
|
= note: for more information, visit https://doc.rust-lang.org/book/ch18-02-refutability.html
|
|
|
|
|
help: you might want to use `if let` to ignore the variant that isn't matched
|
|
|
|
|
|
|
|
|
|
|
LL | if let Helper::U(u) = Helper::T(t, []) { /* */ }
|
|
|
|
|
|
|
2018-08-08 07:28:26 -05:00
|
|
|
|
2019-09-01 12:09:59 -05:00
|
|
|
error[E0381]: use of possibly-uninitialized variable: `u`
|
2019-12-11 08:51:28 -06:00
|
|
|
--> $DIR/empty-never-array.rs:12:5
|
2019-04-15 14:54:18 -05:00
|
|
|
|
|
|
|
|
|
LL | u
|
2019-09-01 12:09:59 -05:00
|
|
|
| ^ use of possibly-uninitialized `u`
|
2019-04-15 14:54:18 -05:00
|
|
|
|
2019-08-02 19:08:16 -05:00
|
|
|
error: aborting due to 2 previous errors
|
2018-08-08 07:28:26 -05:00
|
|
|
|
2019-04-15 14:54:18 -05:00
|
|
|
Some errors have detailed explanations: E0005, E0381.
|
|
|
|
|
For more information about an error, try `rustc --explain E0005`.
|
