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

error: this file contains an unclosed delimiter
  --> $DIR/issue-63116.rs:3:18
   |
LL | impl W <s(f;Y(;]
   |          -     - ^
   |          |     |
   |          |     missing open `[` for this delimiter
   |          unclosed delimiter

error: expected one of `!`, `(`, `)`, `+`, `,`, `::`, or `<`, found `;`
  --> $DIR/issue-63116.rs:3:12
   |
LL | impl W <s(f;Y(;]
   |            ^ expected one of 7 possible tokens

error: mismatched closing delimiter: `]`
  --> $DIR/issue-63116.rs:3:14
   |
LL | impl W <s(f;Y(;]
   |              ^ ^ mismatched closing delimiter
   |              |
   |              unclosed delimiter

error: aborting due to 3 previous errors
tweak wording of mismatched delimiter errors 2020-01-03 07:40:15 -06:00			`error: this file contains an unclosed delimiter`
Add test for issue 63116 2019-11-16 08:54:09 -06:00			`--> $DIR/issue-63116.rs:3:18`
			`\|`
			`LL \| impl W <s(f;Y(;]`
Improve unexpected close and mismatch delimiter hint in TokenTreesReader 2023-01-25 21:02:19 -06:00			`\| - - ^`
			`\| \| \|`
			\| \| missing open `[` for this delimiter
tweak wording of mismatched delimiter errors 2020-01-03 07:40:15 -06:00			`\| unclosed delimiter`
Add test for issue 63116 2019-11-16 08:54:09 -06:00
			error: expected one of `!`, `(`, `)`, `+`, `,`, `::`, or `<`, found `;`
			`--> $DIR/issue-63116.rs:3:12`
			`\|`
			`LL \| impl W <s(f;Y(;]`
			`\| ^ expected one of 7 possible tokens`

Avoid `;` -> `,` recovery and unclosed `}` recovery from being too verbose Those two recovery attempts have a very bad interaction that causes too unnecessary output. Add a simple gate to avoid interpreting a `;` as a `,` when there are unclosed braces. 2021-04-08 21:12:00 -05:00			error: mismatched closing delimiter: `]`
Point at unclosed delimiters as part of the primary MultiSpan Both the place where the parser encounters a needed closed delimiter and the unclosed opening delimiter are important, so they should get the same level of highlighting in the output. 2021-08-27 05:57:28 -05:00			`--> $DIR/issue-63116.rs:3:14`
Add test for issue 63116 2019-11-16 08:54:09 -06:00			`\|`
			`LL \| impl W <s(f;Y(;]`
Point at unclosed delimiters as part of the primary MultiSpan Both the place where the parser encounters a needed closed delimiter and the unclosed opening delimiter are important, so they should get the same level of highlighting in the output. 2021-08-27 05:57:28 -05:00			`\| ^ ^ mismatched closing delimiter`
Add test for issue 63116 2019-11-16 08:54:09 -06:00			`\| \|`
			`\| unclosed delimiter`

			`error: aborting due to 3 previous errors`