rust/tests/ui/pattern/usefulness/slice-patterns-exhaustiveness.stderr

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

264 lines
9.4 KiB
Plaintext
Raw Normal View History

2019-11-16 10:18:46 -06:00
error[E0004]: non-exhaustive patterns: `&[false, _]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:8:11
2019-11-16 10:18:46 -06:00
|
LL | match s2 {
| ^^ pattern `&[false, _]` not covered
|
= note: the matched value is of type `&[bool; 2]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [true, .., true] => {}
LL + &[false, _] => todo!()
|
2019-11-16 10:18:46 -06:00
error[E0004]: non-exhaustive patterns: `&[false, ..]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:12:11
2019-11-16 10:18:46 -06:00
|
LL | match s3 {
| ^^ pattern `&[false, ..]` not covered
2019-11-16 10:18:46 -06:00
|
= note: the matched value is of type `&[bool; 3]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [true, .., true] => {}
LL + &[false, ..] => todo!()
|
2019-11-16 10:18:46 -06:00
error[E0004]: non-exhaustive patterns: `&[false, ..]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:16:11
2019-11-16 10:18:46 -06:00
|
LL | match s10 {
| ^^^ pattern `&[false, ..]` not covered
2019-11-16 10:18:46 -06:00
|
= note: the matched value is of type `&[bool; 10]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [true, .., true] => {}
LL + &[false, ..] => todo!()
|
2019-11-16 10:18:46 -06:00
error[E0004]: non-exhaustive patterns: `&[false, true]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:25:11
|
LL | match s2 {
| ^^ pattern `&[false, true]` not covered
|
= note: the matched value is of type `&[bool; 2]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [.., false] => {}
LL + &[false, true] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[false, .., true]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:30:11
|
LL | match s3 {
| ^^ pattern `&[false, .., true]` not covered
|
= note: the matched value is of type `&[bool; 3]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [.., false] => {}
LL + &[false, .., true] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[false, .., true]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:35:11
|
LL | match s {
| ^ pattern `&[false, .., true]` not covered
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [.., false] => {}
LL + &[false, .., true] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[_, ..]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:42:11
|
LL | match s {
| ^ pattern `&[_, ..]` not covered
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [] => {}
LL + &[_, ..] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[_, _, ..]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:46:11
|
LL | match s {
| ^ pattern `&[_, _, ..]` not covered
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [_] => {}
LL + &[_, _, ..] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[false, ..]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:51:11
|
LL | match s {
| ^ pattern `&[false, ..]` not covered
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [true, ..] => {}
LL + &[false, ..] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[false, _, ..]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:56:11
|
LL | match s {
| ^ pattern `&[false, _, ..]` not covered
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [true, ..] => {}
LL + &[false, _, ..] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[_, .., false]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:62:11
|
LL | match s {
| ^ pattern `&[_, .., false]` not covered
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [.., true] => {}
LL + &[_, .., false] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[_, _, .., true]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:69:11
2019-10-05 16:57:52 -05:00
|
LL | match s {
| ^ pattern `&[_, _, .., true]` not covered
2019-10-05 16:57:52 -05:00
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [.., false] => {}
LL + &[_, _, .., true] => todo!()
|
2019-10-05 16:57:52 -05:00
error[E0004]: non-exhaustive patterns: `&[true, _, .., _]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:76:11
2019-10-05 16:57:52 -05:00
|
LL | match s {
| ^ pattern `&[true, _, .., _]` not covered
2019-10-05 16:57:52 -05:00
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ [false, .., false] => {}
LL + &[true, _, .., _] => todo!()
|
2019-10-05 16:57:52 -05:00
error[E0004]: non-exhaustive patterns: `&[]` and `&[_, _, ..]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:85:11
2019-11-17 16:25:51 -06:00
|
LL | match s {
| ^ patterns `&[]` and `&[_, _, ..]` not covered
2019-11-17 16:25:51 -06:00
|
= note: the matched value is of type `&[bool]`
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
|
LL ~ &[true] => {}
LL + &[] | &[_, _, ..] => todo!()
|
2019-11-17 16:25:51 -06:00
error[E0004]: non-exhaustive patterns: `&[]` and `&[_, _, ..]` not covered
2019-12-29 18:23:42 -06:00
--> $DIR/slice-patterns-exhaustiveness.rs:89:11
2019-11-17 16:25:51 -06:00
|
LL | match s {
| ^ patterns `&[]` and `&[_, _, ..]` not covered
|
= note: the matched value is of type `&[bool]`
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
|
LL ~ CONST => {}
LL + &[] | &[_, _, ..] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[]` and `&[_, _, ..]` not covered
--> $DIR/slice-patterns-exhaustiveness.rs:93:11
|
LL | match s {
| ^ patterns `&[]` and `&[_, _, ..]` not covered
|
= note: the matched value is of type `&[bool]`
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
|
LL ~ &[false] => {}
LL + &[] | &[_, _, ..] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[]` and `&[_, _, ..]` not covered
--> $DIR/slice-patterns-exhaustiveness.rs:98:11
|
LL | match s {
| ^ patterns `&[]` and `&[_, _, ..]` not covered
|
= note: the matched value is of type `&[bool]`
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
|
LL ~ CONST => {}
LL + &[] | &[_, _, ..] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[_, _, ..]` not covered
--> $DIR/slice-patterns-exhaustiveness.rs:103:11
|
LL | match s {
| ^ pattern `&[_, _, ..]` not covered
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ CONST => {}
LL + &[_, _, ..] => todo!()
|
error[E0004]: non-exhaustive patterns: `&[false]` not covered
--> $DIR/slice-patterns-exhaustiveness.rs:108:11
|
LL | match s {
| ^ pattern `&[false]` not covered
2019-11-17 16:25:51 -06:00
|
= note: the matched value is of type `&[bool]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ &[_, _, ..] => {}
LL + &[false] => todo!()
|
2019-11-17 16:25:51 -06:00
error[E0004]: non-exhaustive patterns: `&[false]` not covered
--> $DIR/slice-patterns-exhaustiveness.rs:121:11
2019-11-17 16:25:51 -06:00
|
LL | match s1 {
| ^^ pattern `&[false]` not covered
2019-11-17 16:25:51 -06:00
|
= note: the matched value is of type `&[bool; 1]`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
|
LL ~ CONST1 => {}
LL + &[false] => todo!()
|
2019-11-17 16:25:51 -06:00
error: aborting due to 20 previous errors
For more information about this error, try `rustc --explain E0004`.