rust/tests/ui/rfcs/rfc-2565-param-attrs/param-attrs-2018.stderr

error: expected one of `:`, `@`, or `|`, found `)`
  --> $DIR/param-attrs-2018.rs:3:41
   |
LL | trait Trait2015 { fn foo(#[allow(C)] i32); }
   |                                         ^ 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 | trait Trait2015 { fn foo(#[allow(C)] self: i32); }
   |                                      +++++
help: if this is a parameter name, give it a type
   |
LL | trait Trait2015 { fn foo(#[allow(C)] i32: TypeName); }
   |                                         ++++++++++
help: if this is a type, explicitly ignore the parameter name
   |
LL | trait Trait2015 { fn foo(#[allow(C)] _: i32); }
   |                                      ++

error: aborting due to 1 previous error
parser: gracefully handle `fn foo(A \| B: type)`. 2019-08-24 21:39:28 -05:00			error: expected one of `:`, `@`, or `\|`, found `)`
Stabilize `param_attrs` in Rust 1.39.0 2019-08-29 18:44:30 -05:00			`--> $DIR/param-attrs-2018.rs:3:41`
Allow attributes in formal function parameters 2019-06-09 05:58:40 -05:00			`\|`
			`LL \| trait Trait2015 { fn foo(#[allow(C)] i32); }`
Remove "here" from "expected one of X here" 2019-10-28 13:08:53 -05:00			\| ^ expected one of `:`, `@`, or `\|`
Allow attributes in formal function parameters 2019-06-09 05:58:40 -05:00			`\|`
			`= note: anonymous parameters are removed in the 2018 edition (see RFC 1685)`
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 09:17:50 -05:00			help: if this is a `self` type, give it a parameter name
			`\|`
			`LL \| trait Trait2015 { fn foo(#[allow(C)] self: i32); }`
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 05:53:43 -05:00			`\| +++++`
Fix wording for anonymous parameter name help 2020-06-27 22:55:42 -05:00			`help: if this is a parameter name, give it a type`
Allow attributes in formal function parameters 2019-06-09 05:58:40 -05:00			`\|`
			`LL \| trait Trait2015 { fn foo(#[allow(C)] i32: TypeName); }`
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 05:53:43 -05:00			`\| ++++++++++`
Allow attributes in formal function parameters 2019-06-09 05:58:40 -05:00			`help: if this is a type, explicitly ignore the parameter name`
			`\|`
			`LL \| trait Trait2015 { fn foo(#[allow(C)] _: i32); }`
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 05:53:43 -05:00			`\| ++`
Allow attributes in formal function parameters 2019-06-09 05:58:40 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Allow attributes in formal function parameters 2019-06-09 05:58:40 -05:00