rust/tests/ui/parser/issues/issue-62660.stderr

error: expected one of `!`, `(`, `+`, `,`, `::`, `<`, or `>`, found `)`
  --> $DIR/issue-62660.rs:7:38
   |
LL |     pub fn foo(_: i32, self: Box<Self) {}
   |                                      ^ expected one of 7 possible tokens
   |
help: you might have meant to end the type parameters here
   |
LL |     pub fn foo(_: i32, self: Box<Self>) {}
   |                                      +

error: aborting due to previous error
Improves parser diagnostics, fixes #93867 2022-05-01 12:05:35 -05:00			error: expected one of `!`, `(`, `+`, `,`, `::`, `<`, or `>`, found `)`
Don't drop DiagnosticBuilder if parsing fails If the explicitly given type of a `self` parameter fails to parse correctly, we need to propagate the error rather than dropping it and causing an ICE. Fixes #62660. 2019-07-13 19:34:06 -05:00			`--> $DIR/issue-62660.rs:7:38`
			`\|`
			`LL \| pub fn foo(_: i32, self: Box<Self) {}`
Improves parser diagnostics, fixes #93867 2022-05-01 12:05:35 -05:00			`\| ^ expected one of 7 possible tokens`
Provide suggestion for missing `>` in a type parameter list When encountering an inproperly terminated type parameter list, provide a suggestion to close it after the last non-constraint type parameter that was successfully parsed. Fix #94058. 2022-03-01 13:40:48 -06:00			`\|`
			`help: you might have meant to end the type parameters here`
			`\|`
			`LL \| pub fn foo(_: i32, self: Box<Self>) {}`
			`\| +`
Don't drop DiagnosticBuilder if parsing fails If the explicitly given type of a `self` parameter fails to parse correctly, we need to propagate the error rather than dropping it and causing an ICE. Fixes #62660. 2019-07-13 19:34:06 -05:00
			`error: aborting due to previous error`