rust/compiler/rustc_parse/src/parser/expr.rs, branch 1.52.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.52.02021-03-16T08:41:24+00:00ast: Reduce size of `ExprKind` by boxing fields of `ExprKind::Struct`2021-03-16T08:41:24+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2021-03-16T00:15:53+00:00urn:sha1:d1522b39dded68a3c442bed0b0a231020c6e2291ast/hir: Rename field-related structures2021-03-16T08:41:24+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2021-03-15T21:36:07+00:00urn:sha1:b25d3ba78118033b3f25b6de7a32e210d113872c
StructField -> FieldDef ("field definition")
Field -> ExprField ("expression field", not "field expression")
FieldPat -> PatField ("pattern field", not "field pattern")
Also rename visiting and other methods working on them.
Detect match arm body without braces2021-03-03T20:17:26+00:00Esteban Küberesteban@kuber.com.ar2021-02-26T03:29:50+00:00urn:sha1:ae494d147af627537097f10f21cf961e4c1c6f38
Fix #82524.
remove unneccessary wrapping of return value in mk_await_expr()2021-02-21T12:01:01+00:00Matthias Krügermatthias.krueger@famsik.de2021-02-21T12:01:01+00:00urn:sha1:00bc134e43f30142ea5208dc70dce8ef1e6ac3carustc_parse: remove unneccessary wrapping of return value in fn mk_range() which would always return Ok(..)2021-02-21T11:54:49+00:00Matthias Krügermatthias.krueger@famsik.de2021-02-21T11:54:49+00:00urn:sha1:12080dc3a3ebee0e343d528ca15835ac2d4c75c7Rollup merge of #82236 - matthiaskrgr:useless_conv, r=jyn5142021-02-18T15:57:40+00:00Dylan DPCdylan.dpc@gmail.com2021-02-18T15:57:40+00:00urn:sha1:04df75a4292a8bbf096fd316d0544a5a95b51e9b
avoid converting types into themselves (clippy::useless_conversion)
avoid converting types into themselves (clippy::useless_conversion)2021-02-17T19:37:09+00:00Matthias Krügermatthias.krueger@famsik.de2021-02-17T19:37:09+00:00urn:sha1:ec50a2086a7263b24795f70cfefb3a83737599f7Simplify pattern grammar by allowing nested leading vert2021-02-15T18:07:54+00:00markmarkm@cs.wisc.edu2021-02-08T02:40:33+00:00urn:sha1:aee1e59e6f00876a881e9d8c2ff00e0f11f896eb
Along the way, we also implement a handful of diagnostics improvements
and fixes, particularly with respect to the special handling of `||` in
place of `|` and when there are leading verts in function params, which
don't allow top-level or-patterns anyway.
Address review comments2021-02-13T18:04:54+00:00Aaron Hillaa1ronham@gmail.com2021-02-13T17:42:43+00:00urn:sha1:3321d701617d5ba3ef348d9273f5fcca126d8f04Require passing an `AttrWrapper` to `collect_tokens_trailing_token`2021-02-13T17:07:15+00:00Aaron Hillaa1ronham@gmail.com2021-01-22T18:28:08+00:00urn:sha1:0b411f56e1a539e2388e9a983feb45f362923dc5
This is a pure refactoring split out from #80689.
It represents the most invasive part of that PR, requiring changes in
every caller of `parse_outer_attributes`
In order to eagerly expand `#[cfg]` attributes while preserving the
original `TokenStream`, we need to know the range of tokens that
corresponds to every attribute target. This is accomplished by making
`parse_outer_attributes` return an opaque `AttrWrapper` struct. An
`AttrWrapper` must be converted to a plain `AttrVec` by passing it to
`collect_tokens_trailing_token`. This makes it difficult to accidentally
construct an AST node with attributes without calling `collect_tokens_trailing_token`,
since AST nodes store an `AttrVec`, not an `AttrWrapper`.
As a result, we now call `collect_tokens_trailing_token` for attribute
targets which only support inert attributes, such as generic arguments
and struct fields. Currently, the constructed `LazyTokenStream` is
simply discarded. Future PRs will record the token range corresponding
to the attribute target, allowing those tokens to be removed from an
enclosing `collect_tokens_trailing_token` call if necessary.