rust/compiler/rustc_parse/src/parser, branch 1.84.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.84.02024-11-20T21:22:17+00:00Remove `ErrorGuaranteed` retval from `error_unexpected_after_dot`.2024-11-20T21:22:17+00:00Nicholas Nethercoten.nethercote@gmail.com2024-09-20T03:02:14+00:00urn:sha1:03159d4bff6de12f26daee0f6c6890e71407a389
It was added in #130349, but it's not used meaningfully, and causes
difficulties for Nonterminal removal in #124141.
Prepare for invisible delimiters.2024-11-20T21:22:11+00:00Nicholas Nethercoten.nethercote@gmail.com2024-04-16T23:37:00+00:00urn:sha1:cee88f7a3f1c5bc284d0c6a87fb1d5535ebb3af8
Current places where `Interpolated` is used are going to change to
instead use invisible delimiters. This prepares for that.
- It adds invisible delimiter cases to the `can_begin_*`/`may_be_*`
methods and the `failed_to_match_macro` that are equivalent to the
existing `Interpolated` cases.
- It adds panics/asserts in some places where invisible delimiters
should never occur.
- In `Parser::parse_struct_fields` it excludes an ident + invisible
delimiter from special consideration in an error message, because
that's quite different to an ident + paren/brace/bracket.
Add metavariables to `TokenDescription`.2024-11-20T21:16:55+00:00Nicholas Nethercoten.nethercote@gmail.com2024-04-17T22:58:06+00:00urn:sha1:cfafa9380b446b74708986a344172ec48e295740
Pasted metavariables are wrapped in invisible delimiters, which
pretty-print as empty strings, and changing that can break some proc
macros. But error messages saying "expected identifer, found ``" are
bad. So this commit adds support for metavariables in `TokenDescription`
so they print as "metavariable" in error messages, instead of "``".
It's not used meaningfully yet, but will be needed to get rid of
interpolated tokens.
Introduce `InvisibleOrigin` on invisible delimiters.2024-11-20T21:16:54+00:00Nicholas Nethercoten.nethercote@gmail.com2024-04-16T23:59:27+00:00urn:sha1:afe238f66fc9348b8c4a1daacefb93c0ec36296a
It's not used meaningfully yet, but will be needed to get rid of
interpolated tokens.
Auto merge of #132761 - nnethercote:resolve-tweaks, r=petrochenkov2024-11-19T19:54:35+00:00borsbors@rust-lang.org2024-11-19T19:54:35+00:00urn:sha1:ee612c45f00391aff71ec0c52b7fc08fae18c711
Resolve tweaks
A couple of small perf improvements, and some minor refactorings, all in `rustc_resolve`.
r? `@petrochenkov`
Diagnostics for let mut in item context2024-11-17T22:30:11+00:00Kornelkornel@geekhood.net2024-11-17T21:43:55+00:00urn:sha1:7765f23ea14d16fb0182b475a0ec96891058ae24Rollup merge of #133060 - tyrone-wu:removelet-span-suggestion, r=jieyouxu2024-11-17T15:56:09+00:00许杰友 Jieyou Xu (Joe)39484203+jieyouxu@users.noreply.github.com2024-11-17T15:56:09+00:00urn:sha1:0b157e88d7cf021c0ac537c4618b873f962772ac
Trim whitespace in RemoveLet primary span
Separate `RemoveLet` span into primary span for `let` and removal suggestion span for `let `, so that primary span does not include whitespace.
Fixes: #133031
review comment: move logic to new method2024-11-16T20:03:31+00:00Esteban Küberesteban@kuber.com.ar2024-11-16T20:02:27+00:00urn:sha1:6913194b8ea47ebe8e65b627e83f029d0968d8f8Reword suggestion message2024-11-16T20:03:31+00:00Esteban Küberesteban@kuber.com.ar2024-11-16T00:22:54+00:00urn:sha1:c09c73b99622905e8df074b81377c9ca82467dceBetter account for `else if` macro conditions mising an `if`2024-11-16T20:03:31+00:00Esteban Küberesteban@kuber.com.ar2024-11-14T20:39:25+00:00urn:sha1:629a69f3e2728251774f825ff54cb642b38249df
If a macro statement has been parsed after `else`, suggest a missing `if`:
```
error: expected `{`, found `falsy`
--> $DIR/else-no-if.rs:47:12
|
LL | } else falsy! {} {
| ---- ^^^^^
| |
| expected an `if` or a block after this `else`
|
help: add an `if` if this is the condition of a chained `else if` statement
|
LL | } else if falsy! {} {
| ++
```