mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
11c7f632a2
rust/tests/ui/pattern/range-pattern-meant-to-be-slice-rest-pattern.stderr

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

77 lines
2.8 KiB
Plaintext
Raw Normal View History

Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
error: range-to patterns with `...` are not allowed
Stabilize exclusive_range
2024-04-27 19:35:32 -05:00
--> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:17:13
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
|
LL | [_, ...tail] => println!("{tail}"),
Make parse error suggestions verbose and fix spans Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts.
2024-07-05 22:07:46 -05:00
| ^^^
|
help: use `..=` instead
|
LL | [_, ..=tail] => println!("{tail}"),
| ~~~
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
On resolve error of `[rest..]`, suggest `[rest @ ..]` When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 | LL | [1, rest..] => println!("{rest:?}"), | ^^^^ not found in this scope | help: if you meant to collect the rest of the slice in `rest`, use the at operator | LL | [1, rest @ ..] => println!("{rest:?}"), | + ``` Fix #88404.
2023-11-16 18:55:55 -06:00
error[E0425]: cannot find value `rest` in this scope
--> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13
|
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
LL | [1, rest..] => println!("{rest}"),
On resolve error of `[rest..]`, suggest `[rest @ ..]` When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 | LL | [1, rest..] => println!("{rest:?}"), | ^^^^ not found in this scope | help: if you meant to collect the rest of the slice in `rest`, use the at operator | LL | [1, rest @ ..] => println!("{rest:?}"), | + ``` Fix #88404.
2023-11-16 18:55:55 -06:00
| ^^^^ not found in this scope
|
help: if you meant to collect the rest of the slice in `rest`, use the at operator
|
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
LL | [1, rest @ ..] => println!("{rest}"),
On resolve error of `[rest..]`, suggest `[rest @ ..]` When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 | LL | [1, rest..] => println!("{rest:?}"), | ^^^^ not found in this scope | help: if you meant to collect the rest of the slice in `rest`, use the at operator | LL | [1, rest @ ..] => println!("{rest:?}"), | + ``` Fix #88404.
2023-11-16 18:55:55 -06:00
| +
error[E0425]: cannot find value `rest` in this scope
--> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:35
|
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
LL | [1, rest..] => println!("{rest}"),
| ^^^^ not found in this scope
error[E0425]: cannot find value `tail` in this scope
--> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:11:15
|
LL | [_, ..tail] => println!("{tail}"),
| ^^^^ not found in this scope
|
help: if you meant to collect the rest of the slice in `tail`, use the at operator
|
LL | [_, tail @ ..] => println!("{tail}"),
| ~~~~~~~~~
error[E0425]: cannot find value `tail` in this scope
--> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:11:35
|
LL | [_, ..tail] => println!("{tail}"),
On resolve error of `[rest..]`, suggest `[rest @ ..]` When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 | LL | [1, rest..] => println!("{rest:?}"), | ^^^^ not found in this scope | help: if you meant to collect the rest of the slice in `rest`, use the at operator | LL | [1, rest @ ..] => println!("{rest:?}"), | + ``` Fix #88404.
2023-11-16 18:55:55 -06:00
| ^^^^ not found in this scope
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
error[E0425]: cannot find value `tail` in this scope
Stabilize exclusive_range
2024-04-27 19:35:32 -05:00
--> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:17:16
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
|
LL | [_, ...tail] => println!("{tail}"),
| ^^^^ not found in this scope
|
help: if you meant to collect the rest of the slice in `tail`, use the at operator
|
LL | [_, tail @ ..] => println!("{tail}"),
| ~~~~~~~~~
error[E0425]: cannot find value `tail` in this scope
Stabilize exclusive_range
2024-04-27 19:35:32 -05:00
--> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:17:36
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
|
LL | [_, ...tail] => println!("{tail}"),
| ^^^^ not found in this scope
On resolve error of `[rest..]`, suggest `[rest @ ..]` When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 | LL | [1, rest..] => println!("{rest:?}"), | ^^^^ not found in this scope | help: if you meant to collect the rest of the slice in `rest`, use the at operator | LL | [1, rest @ ..] => println!("{rest:?}"), | + ``` Fix #88404.
2023-11-16 18:55:55 -06:00
error[E0658]: `X..` patterns in slices are experimental
--> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13
|
Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved
2024-02-02 18:32:01 -06:00
LL | [1, rest..] => println!("{rest}"),
On resolve error of `[rest..]`, suggest `[rest @ ..]` When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 | LL | [1, rest..] => println!("{rest:?}"), | ^^^^ not found in this scope | help: if you meant to collect the rest of the slice in `rest`, use the at operator | LL | [1, rest @ ..] => println!("{rest:?}"), | + ``` Fix #88404.
2023-11-16 18:55:55 -06:00
| ^^^^^^
|
= note: see issue #67264 <https://github.com/rust-lang/rust/issues/67264> for more information
= help: add `#![feature(half_open_range_patterns_in_slices)]` to the crate attributes to enable
Bless tests Update tests
2024-01-10 00:39:02 -06:00
= note: this compiler was built on YYYY-MM-DD; consider upgrading it if it is out of date
On resolve error of `[rest..]`, suggest `[rest @ ..]` When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 | LL | [1, rest..] => println!("{rest:?}"), | ^^^^ not found in this scope | help: if you meant to collect the rest of the slice in `rest`, use the at operator | LL | [1, rest @ ..] => println!("{rest:?}"), | + ``` Fix #88404.
2023-11-16 18:55:55 -06:00
Stabilize exclusive_range
2024-04-27 19:35:32 -05:00
error: aborting due to 8 previous errors
On resolve error of `[rest..]`, suggest `[rest @ ..]` When writing a pattern to collect multiple entries of a slice in a single binding, it is easy to misremember or typo the appropriate syntax to do so, instead writing the experimental `X..` pattern syntax. When we encounter a resolve error because `X` isn't available, we suggest `X @ ..` as an alternative. ``` error[E0425]: cannot find value `rest` in this scope --> $DIR/range-pattern-meant-to-be-slice-rest-pattern.rs:3:13 | LL | [1, rest..] => println!("{rest:?}"), | ^^^^ not found in this scope | help: if you meant to collect the rest of the slice in `rest`, use the at operator | LL | [1, rest @ ..] => println!("{rest:?}"), | + ``` Fix #88404.
2023-11-16 18:55:55 -06:00
Some errors have detailed explanations: E0425, E0658.
For more information about an error, try `rustc --explain E0425`.
Reference in New Issue Copy Permalink