rust/compiler/rustc_parse/src/parser/expr.rs, branch 1.55.0

Auto merge of #87071 - inquisitivecrystal:inclusive-range, r=estebank

2021-07-18T05:58:16+00:00

Add diagnostics for mistyped inclusive range Inclusive ranges are correctly typed as `..=`. However, it's quite easy to think of it as being like `==`, and type `..==` instead. This PR adds helpful diagnostics for this case. Resolves #86395 (there are some other cases there, but I think those should probably have separate issues). r? `@estebank`

Suggest a path separator if a stray colon is found in a match arm

2021-07-13T23:15:59+00:00

Co-authored-by: Esteban Kuber

Give a helpful error for the mistake `..==`

2021-07-11T23:51:32+00:00

Auto merge of #85193 - pnkfelix:readd-support-for-inner-attrs-within-match, r=nikomatsakis

2021-06-22T21:17:12+00:00

Re-add support for parsing (and pretty-printing) inner-attributes in match body Re-add support for parsing (and pretty-printing) inner-attributes within body of a `match`. In other words, we can do `match EXPR { #![inner_attr] ARM_1 ARM_2 ... }` again. I believe this unbreaks the only four crates that crater flagged as broken by PR #83312. (I am putting this up so that the lang-team can check it out and decide whether it changes their mind about what to do regarding PR #83312.)

Use `AttrVec` for `Arm`, `FieldDef`, and `Variant`

2021-06-16T23:04:54+00:00

Add support for using qualified paths with structs in expression and pattern

2021-06-10T11:18:41+00:00

position.

parser: Ensure that all nonterminals have tokens after parsing

2021-06-06T11:21:12+00:00

Re-add support for parsing (and pretty-printing) inner-attributes within body of a `match`.

2021-05-11T19:18:09+00:00

In other words, we can do `match EXPR { #![inner_attr] ARM_1 ARM_2 ... }` again. I believe this unbreaks the only four crates that crater flagged as broken by PR 83312. (I am putting this up so that the lang-team can check it out and decide whether it changes their mind about what to do regarding PR 83312.)

parser: Remove support for inner attributes on non-block expressions

2021-05-03T10:33:53+00:00

Implement token-based handling of attributes during expansion

2021-04-11T05:31:36+00:00

This PR modifies the macro expansion infrastructure to handle attributes in a fully token-based manner. As a result: * Derives macros no longer lose spans when their input is modified by eager cfg-expansion. This is accomplished by performing eager cfg-expansion on the token stream that we pass to the derive proc-macro * Inner attributes now preserve spans in all cases, including when we have multiple inner attributes in a row. This is accomplished through the following changes: * New structs `AttrAnnotatedTokenStream` and `AttrAnnotatedTokenTree` are introduced. These are very similar to a normal `TokenTree`, but they also track the position of attributes and attribute targets within the stream. They are built when we collect tokens during parsing. An `AttrAnnotatedTokenStream` is converted to a regular `TokenStream` when we invoke a macro. * Token capturing and `LazyTokenStream` are modified to work with `AttrAnnotatedTokenStream`. A new `ReplaceRange` type is introduced, which is created during the parsing of a nested AST node to make the 'outer' AST node aware of the attributes and attribute target stored deeper in the token stream. * When we need to perform eager cfg-expansion (either due to `#[derive]` or `#[cfg_eval]`), we tokenize and reparse our target, capturing additional information about the locations of `#[cfg]` and `#[cfg_attr]` attributes at any depth within the target. This is a performance optimization, allowing us to perform less work in the typical case where captured tokens never have eager cfg-expansion run.