mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
f2023ac599
rust/src/test/ui/did_you_mean/issue-40396.stderr

30 lines
961 B
Plaintext
Raw Normal View History

Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
error: chained comparison operators require parentheses
Fix rebase and more CI failures
2018-12-26 18:07:00 -06:00
--> $DIR/issue-40396.rs:2:20
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
|
Do not abort compilation if expansion produces errors Fix a number of uncovered deficiencies in diagnostics
2018-12-16 11:23:27 -06:00
LL | (0..13).collect<Vec<i32>>();
| ^^^^^^^^
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
|
= help: use `::<...>` instead of `<...>` if you meant to specify type arguments
output compiler message updated output message is shown in another 'help:' block line with +100 columns formatted test adjusted
2017-10-08 13:01:44 -05:00
= help: or use `(...)` if you meant to specify fn arguments
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
error: chained comparison operators require parentheses
Bail out when encountering likely missing turbofish in parser When encountering a likely intended turbofish without `::`, bubble up the diagnostic instead of emitting it to allow the parser to recover more gracefully and avoid uneccessary type errors that are likely to be wrong.
2019-09-05 15:15:42 -05:00
--> $DIR/issue-40396.rs:7:8
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
|
Do not abort compilation if expansion produces errors Fix a number of uncovered deficiencies in diagnostics
2018-12-16 11:23:27 -06:00
LL | Vec<i32>::new();
| ^^^^^^^
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
|
= help: use `::<...>` instead of `<...>` if you meant to specify type arguments
output compiler message updated output message is shown in another 'help:' block line with +100 columns formatted test adjusted
2017-10-08 13:01:44 -05:00
= help: or use `(...)` if you meant to specify fn arguments
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
error: chained comparison operators require parentheses
Bail out when encountering likely missing turbofish in parser When encountering a likely intended turbofish without `::`, bubble up the diagnostic instead of emitting it to allow the parser to recover more gracefully and avoid uneccessary type errors that are likely to be wrong.
2019-09-05 15:15:42 -05:00
--> $DIR/issue-40396.rs:12:20
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
|
Do not abort compilation if expansion produces errors Fix a number of uncovered deficiencies in diagnostics
2018-12-16 11:23:27 -06:00
LL | (0..13).collect<Vec<i32>();
| ^^^^^^^^
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
|
= help: use `::<...>` instead of `<...>` if you meant to specify type arguments
output compiler message updated output message is shown in another 'help:' block line with +100 columns formatted test adjusted
2017-10-08 13:01:44 -05:00
= help: or use `(...)` if you meant to specify fn arguments
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
Bail out when encountering likely missing turbofish in parser When encountering a likely intended turbofish without `::`, bubble up the diagnostic instead of emitting it to allow the parser to recover more gracefully and avoid uneccessary type errors that are likely to be wrong.
2019-09-05 15:15:42 -05:00
error: aborting due to 3 previous errors
Point out correct turbofish usage on `Foo<Bar<Baz>>` Whenever we parse a chain of binary operations, as long as the first operation is `<` and the subsequent operations are either `>` or `<`, present the following diagnostic help: use `::<...>` instead of `<...>` if you meant to specify type arguments This will lead to spurious recommendations on situations like `2 < 3 < 4` but should be clear from context that the help doesn't apply in that case.
2017-03-13 21:07:47 -05:00
Reference in New Issue Copy Permalink