diff options
| author | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-06-23 08:13:56 +1000 |
|---|---|---|
| committer | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-06-23 15:57:24 +1000 |
| commit | e2aa38e6abf9c2ddd06fb2469628ee488dc49e30 (patch) | |
| tree | 916ea3ce9d427a08737a99094380d0ebc28605df /tests/rustdoc/inline_cross/add-docs.rs | |
| parent | 70fa67c0b2551b68b3d54bdebbb6565c95f25ab7 (diff) | |
| download | rust-e2aa38e6abf9c2ddd06fb2469628ee488dc49e30.tar.gz rust-e2aa38e6abf9c2ddd06fb2469628ee488dc49e30.zip | |
Rework pattern and expression nonterminal kinds.
Merge `PatParam`/`PatWithOr`, and `Expr`/`Expr2021`, for a few reasons.
- It's conceptually nice, because the two pattern kinds and the two
expression kinds are very similar.
- With expressions in particular, there are several places where both
expression kinds get the same treatment.
- It removes one unreachable match arm.
- Most importantly, for #124141 I will need to introduce a new type
`MetaVarKind` that is very similar to `NonterminalKind`, but records a
couple of extra fields for expression metavars. It's nicer to have a
single `MetaVarKind::Expr` expression variant to hold those extra
fields instead of duplicating them across two variants
`MetaVarKind::{Expr,Expr2021}`. And then it makes sense for patterns
to be treated the same way, and for `NonterminalKind` to also be
treated the same way.
I also clarified the comments, because I have long found them a little
hard to understand.
Diffstat (limited to 'tests/rustdoc/inline_cross/add-docs.rs')
0 files changed, 0 insertions, 0 deletions