rust/tests/ui/parser/closure-return-syntax.stderr

error: expected `{`, found `22`
  --> $DIR/closure-return-syntax.rs:5:23
   |
LL |     let x = || -> i32 22;
   |                       ^^ expected `{`
   |
help: you might have meant to write this as part of a block
   |
LL |     let x = || -> i32 { 22 };
   |                       +    +

error: aborting due to 1 previous error
more reuse in block parsing & improve diagnostics. 2020-03-05 05:49:30 +01:00			error: expected `{`, found `22`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 18:33:05 +03:00			`--> $DIR/closure-return-syntax.rs:5:23`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\|`
			`LL \| let x = \|\| -> i32 22;`
Tweak diagnostics * Recover from invalid `'label: ` before block. * Make suggestion to enclose statements in a block multipart. * Point at `match`, `while`, `loop` and `unsafe` keywords when failing to parse their expression. * Do not suggest `{ ; }`. * Do not suggest `\|` when very unlikely to be what was wanted (in `let` statements). 2022-01-12 20:43:24 +00:00			\| ^^ expected `{`
			`\|`
Reword suggestion message 2024-11-16 00:22:54 +00:00			`help: you might have meant to write this as part of a block`
Tweak diagnostics * Recover from invalid `'label: ` before block. * Make suggestion to enclose statements in a block multipart. * Point at `match`, `while`, `loop` and `unsafe` keywords when failing to parse their expression. * Do not suggest `{ ; }`. * Do not suggest `\|` when very unlikely to be what was wanted (in `let` statements). 2022-01-12 20:43:24 +00:00			`\|`
			`LL \| let x = \|\| -> i32 { 22 };`
			`\| + +`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00