rust/tests/ui/parser/pat-lt-bracket-2.stderr

error: expected one of `:`, `@`, or `|`, found `<`
  --> $DIR/pat-lt-bracket-2.rs:1:7
   |
LL | fn a(B<) {}
   |       ^ expected one of `:`, `@`, or `|`
   |
   = note: anonymous parameters are removed in the 2018 edition (see RFC 1685)
help: if this is a `self` type, give it a parameter name
   |
LL | fn a(self: B<) {}
   |      +++++
help: if this is a type, explicitly ignore the parameter name
   |
LL | fn a(_: B<) {}
   |      ++

error: aborting due to previous error
parser: gracefully handle `fn foo(A \| B: type)`. 2019-08-25 04:39:28 +02:00			error: expected one of `:`, `@`, or `\|`, found `<`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 18:33:05 +03:00			`--> $DIR/pat-lt-bracket-2.rs:1:7`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\|`
			`LL \| fn a(B<) {}`
Remove "here" from "expected one of X here" 2019-10-28 11:08:53 -07:00			\| ^ expected one of `:`, `@`, or `\|`
syntax: improve parameter without type suggestions This commit improves the suggestions provided when function parameters do not have types: - A new suggestion is added for arbitrary self types, which suggests adding `self: ` before the type. - Existing suggestions are now provided when a `<` is found where a `:` was expected (previously only `,` and `)` or trait items), this gives suggestions in the case where the unnamed parameter type is generic in a free function. - The suggestion that a type name be provided (e.g. `fn foo(HashMap<u32>)` -> `fn foo(HashMap: TypeName<u32>)`) will no longer occur when a `<` was found instead of `:`. - The ident will not be used for recovery when a `<` was found instead of `:`. Signed-off-by: David Wood <david@davidtw.co> 2019-10-01 15:17:50 +01:00			`\|`
			`= note: anonymous parameters are removed in the 2018 edition (see RFC 1685)`
parser: address review comments re. `self`. 2020-02-02 11:10:27 +01:00			help: if this is a `self` type, give it a parameter name
			`\|`
			`LL \| fn a(self: B<) {}`
Use smaller spans for some structured suggestions Use more accurate suggestion spans for * argument parse error * fully qualified path * missing code block type * numeric casts * E0212 2021-08-10 10:53:43 +00:00			`\| +++++`
syntax: improve parameter without type suggestions This commit improves the suggestions provided when function parameters do not have types: - A new suggestion is added for arbitrary self types, which suggests adding `self: ` before the type. - Existing suggestions are now provided when a `<` is found where a `:` was expected (previously only `,` and `)` or trait items), this gives suggestions in the case where the unnamed parameter type is generic in a free function. - The suggestion that a type name be provided (e.g. `fn foo(HashMap<u32>)` -> `fn foo(HashMap: TypeName<u32>)`) will no longer occur when a `<` was found instead of `:`. - The ident will not be used for recovery when a `<` was found instead of `:`. Signed-off-by: David Wood <david@davidtw.co> 2019-10-01 15:17:50 +01:00			`help: if this is a type, explicitly ignore the parameter name`
			`\|`
			`LL \| fn a(_: B<) {}`
Use smaller spans for some structured suggestions Use more accurate suggestion spans for * argument parse error * fully qualified path * missing code block type * numeric casts * E0212 2021-08-10 10:53:43 +00:00			`\| ++`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00
Make sure all ui/parse tests have `-Z parse-only` Except those testing parsing during macro expansion 2018-10-21 00:38:23 +03:00			`error: aborting due to previous error`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00