mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
107d480892
rust/tests/ui/pattern/usefulness/match-byte-array-patterns-2.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

30 lines
1.2 KiB
Plaintext
Raw Normal View History

Show the values and computation that would overflow a const evaluation or propagation
2020-06-19 11:57:15 -05:00
error[E0004]: non-exhaustive patterns: `&[0_u8..=64_u8, _, _, _]` and `&[66_u8..=u8::MAX, _, _, _]` not covered
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/match-byte-array-patterns-2.rs:4:11
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | match buf {
Show the values and computation that would overflow a const evaluation or propagation
2020-06-19 11:57:15 -05:00
| ^^^ patterns `&[0_u8..=64_u8, _, _, _]` and `&[66_u8..=u8::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
|
non-exhastive diagnostic: add note re. scrutinee type
2020-03-27 00:44:30 -05:00
= note: the matched value is of type `&[u8; 4]`
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 a single arm that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None | Some(_) => todo!(), } ```
2021-12-15 20:14:17 -06:00
|
Perform match checking on THIR.
2023-02-27 11:43:39 -06:00
LL ~ b"AAAA" => {},
When finding a match expr with a single arm that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None | Some(_) => todo!(), } ```
2021-12-15 20:14:17 -06:00
LL + &[0_u8..=64_u8, _, _, _] | &[66_u8..=u8::MAX, _, _, _] => todo!()
|
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
Fix exhaustiveness in case a byte string literal is used at slice type
2020-11-15 07:04:30 -06:00
error[E0004]: non-exhaustive patterns: `&[]`, `&[_]`, `&[_, _]` and 2 more not covered
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/match-byte-array-patterns-2.rs:10:11
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | match buf {
Fix exhaustiveness in case a byte string literal is used at slice type
2020-11-15 07:04:30 -06:00
| ^^^ patterns `&[]`, `&[_]`, `&[_, _]` 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
|
non-exhastive diagnostic: add note re. scrutinee type
2020-03-27 00:44:30 -05:00
= note: the matched value is of type `&[u8]`
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 as shown, or multiple match arms
When finding a match expr with a single arm that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None | Some(_) => todo!(), } ```
2021-12-15 20:14:17 -06:00
|
Perform match checking on THIR.
2023-02-27 11:43:39 -06:00
LL ~ b"AAAA" => {},
When finding a match expr with a single arm that requires more, suggest it Given ```rust match Some(42) { Some(0) => {} } ``` suggest ```rust match Some(42) { Some(0) => {} None | Some(_) => todo!(), } ```
2021-12-15 20:14:17 -06:00
LL + _ => todo!()
|
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0004`.
Reference in New Issue Copy Permalink