about summary refs log tree commit diff
path: root/src/test/ui/parser/expr-as-stmt-2.stderr
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-46/+0
2022-10-05Suggest `.into()` when all other coercion suggestions failMichael Goulet-5/+0
2022-06-16diagnostics: fix trailing spaceklensy-1/+1
2022-02-27Make deref suggestion betterMichael Goulet-0/+5
2021-08-11Modify structured suggestion outputEsteban Küber-3/+3
* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-07-30Use multispan suggestions more oftenEsteban Küber-2/+5
* Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often
2021-02-21Do not suggest `;` if expression is side effect freeEsteban Küber-8/+0
When a tail expression isn't unit, we previously always suggested adding a trailing `;` to turn it into a statement. This suggestion isn't appropriate for any expression that doesn't have side-effects, as the user will have likely wanted to call something else or do something with the resulting value, instead of just discarding it.
2021-02-21Suggest `return`ing tail expressions that match return typeEsteban Küber-2/+20
Some newcomers are confused by the behavior of tail expressions, interpreting that "leaving out the `;` makes it the return value". To help them go in the right direction, suggest using `return` instead when applicable.
2020-07-22Correctly parse `{} && false` in tail expressionEsteban Küber-0/+33
Fix #74233.