rust/tests/ui/did_you_mean/issue-40396.stderr

error: comparison operators cannot be chained
  --> $DIR/issue-40396.rs:2:20
   |
LL |     (0..13).collect<Vec<i32>>();
   |                    ^   ^
   |
help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
   |
LL |     (0..13).collect::<Vec<i32>>();
   |                    ++

error: comparison operators cannot be chained
  --> $DIR/issue-40396.rs:5:8
   |
LL |     Vec<i32>::new();
   |        ^   ^
   |
help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
   |
LL |     Vec::<i32>::new();
   |        ++

error: comparison operators cannot be chained
  --> $DIR/issue-40396.rs:8:20
   |
LL |     (0..13).collect<Vec<i32>();
   |                    ^   ^
   |
help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
   |
LL |     (0..13).collect::<Vec<i32>();
   |                    ++

error: expected one of `!`, `.`, `::`, `;`, `?`, `else`, `{`, or an operator, found `,`
  --> $DIR/issue-40396.rs:11:43
   |
LL |     let x = std::collections::HashMap<i128, i128>::new();
   |                                           ^ expected one of 8 possible tokens
   |
help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
   |
LL |     let x = std::collections::HashMap::<i128, i128>::new();
   |                                      ++

error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `,`
  --> $DIR/issue-40396.rs:15:39
   |
LL |         std::collections::HashMap<i128, i128>::new()
   |                                       ^ expected one of 8 possible tokens
   |
help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
   |
LL |         std::collections::HashMap::<i128, i128>::new()
   |                                  ++

error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `,`
  --> $DIR/issue-40396.rs:20:39
   |
LL |         std::collections::HashMap<i128, i128>::new();
   |                                       ^ expected one of 8 possible tokens
   |
help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
   |
LL |         std::collections::HashMap::<i128, i128>::new();
   |                                  ++

error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `,`
  --> $DIR/issue-40396.rs:25:39
   |
LL |         std::collections::HashMap<i128, i128>::new(1, 2);
   |                                       ^ expected one of 8 possible tokens
   |
help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
   |
LL |         std::collections::HashMap::<i128, i128>::new(1, 2);
   |                                  ++

error[E0308]: mismatched types
  --> $DIR/issue-40396.rs:13:17
   |
LL |     let x: () = 42;
   |            --   ^^ expected `()`, found integer
   |            |
   |            expected due to this

error[E0308]: mismatched types
  --> $DIR/issue-40396.rs:18:17
   |
LL |     let x: () = 42;
   |            --   ^^ expected `()`, found integer
   |            |
   |            expected due to this

error[E0308]: mismatched types
  --> $DIR/issue-40396.rs:22:21
   |
LL |         let x: () = 42;
   |                --   ^^ expected `()`, found integer
   |                |
   |                expected due to this

error[E0308]: mismatched types
  --> $DIR/issue-40396.rs:27:21
   |
LL |         let x: () = 32;
   |                --   ^^ expected `()`, found integer
   |                |
   |                expected due to this

error: aborting due to 11 previous errors

For more information about this error, try `rustc --explain E0308`.
Add suggestions when encountering chained comparisons 2020-01-10 18:19:09 -06:00			`error: comparison operators cannot be chained`
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>>();`
Tweak chained operators diagnostic Use more selective spans Improve suggestion output Be more selective when displaying suggestions Silence some knock-down type errors 2020-03-09 22:21:37 -05:00			`\| ^ ^`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
Fix suggesting turbofish with lifetime arguments 2022-01-13 17:44:17 -06:00			help: use `::<...>` instead of `<...>` to specify lifetime, type, or const 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			`\|`
When encountering chained operators use heuristics to recover from bad turbofish 2019-09-29 21:07:26 -05:00			`LL \| (0..13).collect::<Vec<i32>>();`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++`
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
Add suggestions when encountering chained comparisons 2020-01-10 18:19:09 -06:00			`error: comparison operators cannot be chained`
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			`--> $DIR/issue-40396.rs:5: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();`
Tweak chained operators diagnostic Use more selective spans Improve suggestion output Be more selective when displaying suggestions Silence some knock-down type errors 2020-03-09 22:21:37 -05:00			`\| ^ ^`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
Fix suggesting turbofish with lifetime arguments 2022-01-13 17:44:17 -06:00			help: use `::<...>` instead of `<...>` to specify lifetime, type, or const 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			`\|`
Account for missing turbofish in paths too 2019-09-30 14:36:44 -05:00			`LL \| Vec::<i32>::new();`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++`
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
Add suggestions when encountering chained comparisons 2020-01-10 18:19:09 -06:00			`error: comparison operators cannot be chained`
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			`--> $DIR/issue-40396.rs:8: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>();`
Tweak chained operators diagnostic Use more selective spans Improve suggestion output Be more selective when displaying suggestions Silence some knock-down type errors 2020-03-09 22:21:37 -05:00			`\| ^ ^`
Add suggestions when encountering chained comparisons 2020-01-10 18:19:09 -06:00			`\|`
Fix suggesting turbofish with lifetime arguments 2022-01-13 17:44:17 -06:00			help: use `::<...>` instead of `<...>` to specify lifetime, type, or const 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			`\|`
When encountering chained operators use heuristics to recover from bad turbofish 2019-09-29 21:07:26 -05:00			`LL \| (0..13).collect::<Vec<i32>();`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++`
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
Fix tests 2021-08-01 19:55:48 -05:00			error: expected one of `!`, `.`, `::`, `;`, `?`, `else`, `{`, or an operator, found `,`
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			`--> $DIR/issue-40396.rs:11:43`
			`\|`
			`LL \| let x = std::collections::HashMap<i128, i128>::new();`
Fix tests 2021-08-01 19:55:48 -05:00			`\| ^ expected one of 8 possible tokens`
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			`\|`
Fix suggesting turbofish with lifetime arguments 2022-01-13 17:44:17 -06:00			help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			`\|`
			`LL \| let x = std::collections::HashMap::<i128, i128>::new();`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++`
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00
			error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `,`
			`--> $DIR/issue-40396.rs:15:39`
			`\|`
			`LL \| std::collections::HashMap<i128, i128>::new()`
			`\| ^ expected one of 8 possible tokens`
			`\|`
Fix suggesting turbofish with lifetime arguments 2022-01-13 17:44:17 -06:00			help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			`\|`
			`LL \| std::collections::HashMap::<i128, i128>::new()`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++`
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00
			error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `,`
			`--> $DIR/issue-40396.rs:20:39`
			`\|`
			`LL \| std::collections::HashMap<i128, i128>::new();`
			`\| ^ expected one of 8 possible tokens`
			`\|`
Fix suggesting turbofish with lifetime arguments 2022-01-13 17:44:17 -06:00			help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			`\|`
			`LL \| std::collections::HashMap::<i128, i128>::new();`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++`
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00
			error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `,`
			`--> $DIR/issue-40396.rs:25:39`
			`\|`
			`LL \| std::collections::HashMap<i128, i128>::new(1, 2);`
			`\| ^ expected one of 8 possible tokens`
			`\|`
Fix suggesting turbofish with lifetime arguments 2022-01-13 17:44:17 -06:00			help: use `::<...>` instead of `<...>` to specify lifetime, type, or const arguments
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			`\|`
			`LL \| std::collections::HashMap::<i128, i128>::new(1, 2);`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| ++`
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00
			`error[E0308]: mismatched types`
			`--> $DIR/issue-40396.rs:13:17`
			`\|`
			`LL \| let x: () = 42;`
			\| -- ^^ expected `()`, found integer
			`\| \|`
			`\| expected due to this`

			`error[E0308]: mismatched types`
			`--> $DIR/issue-40396.rs:18:17`
			`\|`
			`LL \| let x: () = 42;`
			\| -- ^^ expected `()`, found integer
			`\| \|`
			`\| expected due to this`

			`error[E0308]: mismatched types`
			`--> $DIR/issue-40396.rs:22:21`
			`\|`
			`LL \| let x: () = 42;`
			\| -- ^^ expected `()`, found integer
			`\| \|`
			`\| expected due to this`

			`error[E0308]: mismatched types`
			`--> $DIR/issue-40396.rs:27:21`
			`\|`
			`LL \| let x: () = 32;`
			\| -- ^^ expected `()`, found integer
			`\| \|`
			`\| expected due to this`

			`error: aborting due to 11 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
Detect turbofish with multiple type params missing leading `::` Fix #76072. 2020-08-31 12:24:37 -05:00			For more information about this error, try `rustc --explain E0308`.