2018-05-19 19:55:05 -05:00
|
|
|
error: unreachable pattern
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:23:9
|
2018-05-19 19:55:05 -05:00
|
|
|
|
|
|
|
|
|
LL | 200 => {} //~ ERROR unreachable pattern
|
|
|
|
|
| ^^^
|
|
|
|
|
|
|
|
|
|
|
note: lint level defined here
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:4:9
|
2018-05-19 19:55:05 -05:00
|
|
|
|
|
|
|
|
|
LL | #![deny(unreachable_patterns)]
|
|
|
|
|
| ^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
2018-05-25 03:47:37 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `128u8..=255u8` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:28:11
|
2018-05-19 19:55:05 -05:00
|
|
|
|
|
2018-05-21 19:03:05 -05:00
|
|
|
LL | match x { //~ ERROR non-exhaustive patterns
|
2018-05-25 03:47:37 -05:00
|
|
|
| ^ pattern `128u8..=255u8` 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-05-19 19:55:05 -05:00
|
|
|
|
2018-05-25 03:47:37 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `11u8..=19u8`, `31u8..=34u8`, `36u8..=69u8` and 1 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:33:11
|
2018-05-19 19:55:05 -05:00
|
|
|
|
|
|
|
|
|
LL | match x { //~ ERROR non-exhaustive patterns
|
2018-05-25 03:47:37 -05:00
|
|
|
| ^ patterns `11u8..=19u8`, `31u8..=34u8`, `36u8..=69u8` and 1 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-05-19 19:55:05 -05:00
|
|
|
|
|
|
|
|
error: unreachable pattern
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:44:9
|
2018-05-19 19:55:05 -05:00
|
|
|
|
|
|
|
|
|
LL | -2..=20 => {} //~ ERROR unreachable pattern
|
|
|
|
|
| ^^^^^^^
|
|
|
|
|
|
2018-05-25 03:47:37 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `-128i8..=-8i8`, `-6i8`, `121i8..=124i8` and 1 more not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:41:11
|
2018-05-19 19:55:05 -05:00
|
|
|
|
|
|
|
|
|
LL | match x { //~ ERROR non-exhaustive patterns
|
2018-05-25 03:47:37 -05:00
|
|
|
| ^ patterns `-128i8..=-8i8`, `-6i8`, `121i8..=124i8` and 1 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-05-19 19:55:05 -05:00
|
|
|
|
2018-05-21 19:03:05 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `-128i8` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:82:11
|
2018-05-21 19:03:05 -05:00
|
|
|
|
|
|
|
|
|
LL | match 0i8 { //~ ERROR non-exhaustive patterns
|
|
|
|
|
| ^^^ pattern `-128i8` 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-05-21 19:03:05 -05:00
|
|
|
|
|
|
|
|
error[E0004]: non-exhaustive patterns: `0i16` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:90:11
|
2018-05-21 19:03:05 -05:00
|
|
|
|
|
|
|
|
|
LL | match 0i16 { //~ ERROR non-exhaustive patterns
|
|
|
|
|
| ^^^^ pattern `0i16` 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-05-21 19:03:05 -05:00
|
|
|
|
2018-06-02 04:53:47 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `128u8..=255u8` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:108:11
|
2018-06-02 04:53:47 -05:00
|
|
|
|
|
|
|
|
|
LL | match 0u8 { //~ ERROR non-exhaustive patterns
|
|
|
|
|
| ^^^ pattern `128u8..=255u8` 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-06-02 04:53:47 -05:00
|
|
|
|
2018-08-12 14:47:23 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `(0u8, Some(_))` and `(2u8..=255u8, Some(_))` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:120:11
|
2018-08-12 14:47:23 -05:00
|
|
|
|
|
|
|
|
|
LL | match (0u8, Some(())) { //~ ERROR non-exhaustive patterns
|
|
|
|
|
| ^^^^^^^^^^^^^^^ patterns `(0u8, Some(_))` and `(2u8..=255u8, Some(_))` 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-08-12 14:47:23 -05:00
|
|
|
|
2018-08-13 21:02:31 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `(126u8..=127u8, false)` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:125:11
|
2018-08-13 21:02:31 -05:00
|
|
|
|
|
|
|
|
|
LL | match (0u8, true) { //~ ERROR non-exhaustive patterns
|
|
|
|
|
| ^^^^^^^^^^^ pattern `(126u8..=127u8, 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-08-13 21:02:31 -05:00
|
|
|
|
2018-08-21 15:04:19 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `340282366920938463463374607431768211455u128` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:145:11
|
2018-08-21 15:04:19 -05:00
|
|
|
|
|
|
|
|
|
LL | match 0u128 { //~ ERROR non-exhaustive patterns
|
|
|
|
|
| ^^^^^ pattern `340282366920938463463374607431768211455u128` 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-08-21 15:04:19 -05:00
|
|
|
|
2018-08-21 17:55:57 -05:00
|
|
|
error[E0004]: non-exhaustive patterns: `5u128..=340282366920938463463374607431768211455u128` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:149:11
|
2018-08-21 17:55:57 -05:00
|
|
|
|
|
|
|
|
|
LL | match 0u128 { //~ ERROR non-exhaustive patterns
|
|
|
|
|
| ^^^^^ pattern `5u128..=340282366920938463463374607431768211455u128` 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-08-21 17:55:57 -05:00
|
|
|
|
|
|
|
|
error[E0004]: non-exhaustive patterns: `0u128..=3u128` not covered
|
2018-12-25 09:56:47 -06:00
|
|
|
--> $DIR/exhaustive_integer_patterns.rs:153:11
|
2018-08-21 17:55:57 -05:00
|
|
|
|
|
|
|
|
|
LL | match 0u128 { //~ ERROR non-exhaustive patterns
|
|
|
|
|
| ^^^^^ pattern `0u128..=3u128` 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
|
|
|
|
|
|
|
|
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
|
2018-08-21 17:55:57 -05:00
|
|
|
|
|
|
|
|
error: aborting due to 13 previous errors
|
2018-05-19 19:55:05 -05:00
|
|
|
|
|
|
|
|
For more information about this error, try `rustc --explain E0004`.
|
