diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2022-05-24 15:58:24 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-05-24 15:58:24 +0200 |
| commit | 0531521dbb470f17d2ebd68e558f41f936ec2e24 (patch) | |
| tree | 913d71c3efef2f5511908a7bf5a440710bf6dcff /compiler/rustc_codegen_gcc | |
| parent | 3569a426b5d561076c4dc43828efd05be82a07f2 (diff) | |
| parent | 9be37b2d3fc0b3852a7f9b134197dec895030201 (diff) | |
| download | rust-0531521dbb470f17d2ebd68e558f41f936ec2e24.tar.gz rust-0531521dbb470f17d2ebd68e558f41f936ec2e24.zip | |
Rollup merge of #97298 - compiler-errors:if-else-stmt-braces, r=davidtwco
Parse expression after `else` as a condition if followed by `{`
Fixes #49361.
Two things:
1. This wording needs help. I can never find a natural/intuitive phrasing when I write diagnostics :sweat_smile:
2. Do we even want to show the "wrap in braces" case? I would assume most of the time the "add an `if`" case is the right one.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions