diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-04-14 18:15:31 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-14 18:15:31 +0200 |
| commit | bf49dfc943406c086d31ecf381eea628d13fcc2e (patch) | |
| tree | 8ac64bc587efbe72e194cb9d0db0d1093b617f10 /compiler/rustc_interface/src/errors.rs | |
| parent | a4adc005a19a745b1e9159841a1cbd45fca5c9af (diff) | |
| parent | 6dfbe7c986d55a5a48f625d37d4576092e5638eb (diff) | |
| download | rust-bf49dfc943406c086d31ecf381eea628d13fcc2e.tar.gz rust-bf49dfc943406c086d31ecf381eea628d13fcc2e.zip | |
Rollup merge of #139392 - compiler-errors:raw-expr, r=oli-obk
Detect and provide suggestion for `&raw EXPR` When emitting an error in the parser, and we detect that the previous token was `raw` and we *could* have consumed `const`/`mut`, suggest that this may have been a mistyped raw ref expr. To do this, we add `const`/`mut` to the expected token set when parsing `&raw` as an expression (which does not affect the "good path" of parsing, for the record). This is kind of a rudimentary error improvement, since it doesn't actually attempt to recover anything, leading to some other knock-on errors b/c we still treat `&raw` as the expression that was parsed... but at least we add the suggestion! I don't think the parser grammar means we can faithfully recover `&raw EXPR` early, i.e. during `parse_expr_borrow`. Fixes #133231
Diffstat (limited to 'compiler/rustc_interface/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
