rust/tests/ui/parser/match-arrows-block-then-binop.stderr

error: expected pattern, found `+`
  --> $DIR/match-arrows-block-then-binop.rs:5:9
   |
LL |       } + 5
   |         ^ expected pattern
   |
help: parentheses are required to parse this as an expression
   |
LL ~       0 => ({
LL |         0
LL ~       }) + 5
   |

error: aborting due to previous error
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			error: expected pattern, found `+`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 09:33:05 -06:00			`--> $DIR/match-arrows-block-then-binop.rs:5:9`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| } + 5`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00			`\| ^ expected pattern`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
fix typo 2019-05-02 17:53:09 -05:00			`help: parentheses are required to parse this as an expression`
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar. 2019-04-22 21:37:23 -05:00			`\|`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`LL ~ 0 => ({`
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar. 2019-04-22 21:37:23 -05:00			`LL \| 0`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`LL ~ }) + 5`
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar. 2019-04-22 21:37:23 -05:00			`\|`
Move parse-fail tests to UI 2018-10-20 15:36:17 -05:00
			`error: aborting due to previous error`