about summary refs log tree commit diff
path: root/tests/ui/parser/bad-let-else-statement.stderr
AgeCommit message (Collapse)AuthorLines
2025-02-10Show diff suggestion format on verbose replacementEsteban Küber-4/+6
``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 | LL | let _ = 2.l; | ^ | help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix | LL - let _ = 2.l; LL + let _ = 2.0f64; | ```
2024-07-07Support tail calls in mir via `TerminatorKind::TailCall`Maybe Waffle-14/+1
2024-05-12Disallow cast with trailing braced macro in let-elseDavid Tolnay-1/+15
2024-05-12Add test of trailing brace in a cast expressionDavid Tolnay-1/+13
2024-05-12Clean up unneeded warnings from let-else syntax testDavid Tolnay-257/+43
2024-04-24Fix tests and blessGary Guo-38/+38
2024-02-08Continue to borrowck even if there were previous errorsOli Scherer-22/+281
2024-01-18Suggest wrapping mac args in parens rather than the whole expressionMichael Goulet-6/+6
2024-01-17Deny braced macro invocations in let-elseMichael Goulet-1/+27
2023-12-14Change expr_trailing_brace to an exhaustive match to force new expression ↵GearsDatapacks-0/+232
kinds to specify whether they contain a brace Add inline const and other possible curly brace expressions to expr_trailing_brace Add tests for `}` before `else` in `let...else` error Change to explicit cases for expressions with optional values when being checked for trailing braces Add tests for more complex cases of `}` before `else` in `let..else` statement Move other possible `}` cases into separate arm and add FIXME for future reference