summary refs log tree commit diff
path: root/src/test/ui/parser/expr-as-stmt.stderr
AgeCommit message (Collapse)AuthorLines
2019-11-18Surround types with backticks in type errorsEsteban Küber-4/+4
2019-11-18Remove E0308 note when primary label has all infoEsteban Küber-12/+0
2019-11-18review comments: tweak prefix stringsEsteban Küber-8/+8
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+1
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-05-02fix typoEsteban Küber-6/+6
2019-04-30Reword ambigous parse error to fit with the current errorEsteban Küber-4/+4
2019-04-29Add test case for #47287Esteban Küber-1/+13
2019-04-29Identify when a stmt could have been parsed as an exprEsteban Küber-0/+80
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.