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

Remove `TrailingToken`.

2024-07-18T07:28:49+00:00

It's used in `Parser::collect_tokens_trailing_token` to decide whether to capture a trailing token. But the callers actually know whether to capture a trailing token, so it's simpler for them to just pass in a bool. Also, the `TrailingToken::Gt` case was weird, because it didn't result in a trailing token being captured. It could have been subsumed by the `TrailingToken::MaybeComma` case, and it effectively is in the new code.

Rollup merge of #127806 - nnethercote:parser-improvements, r=spastorino

2024-07-18T00:53:27+00:00

Some parser improvements I was looking closely at attribute handling in the parser while debugging some issues relating to #124141, and found a few small improvements. ``@spastorino``

Deny keyword lifetimes pre-expansion

2024-07-16T16:06:25+00:00

Fix a comment.

2024-07-16T06:39:19+00:00

Inline and remove `Parser::parse_expr_dot_or_call_with_`.

2024-07-16T06:16:38+00:00

It only has two call sites, and it extremely similar to `Parser::parse_expr_dot_or_call_with`, in both name and behaviour. The only difference is the latter has an `attrs` argument and an `ensure_sufficient_stack` call. We can pass in an empty `attrs` as necessary, as is already done at some `parse_expr_dot_or_call_with` call sites.

Inline and remove `Parser::parse_and_disallow_postfix_after_cast`.

2024-07-16T06:09:36+00:00

It has a single call site. Removing it removes the need for an `ExprKind` check. The commit also clarifies the relevant comment.

Reorder `Parser::parse_expr_dot_or_call_with` arguments.

2024-07-16T05:54:34+00:00

Put `attrs` before `e0` because that matches the order in the source code, where outer attributes appear before expressions.

Make parse error suggestions verbose and fix spans

2024-07-12T03:02:57+00:00

Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts.

Rollup merge of #127103 - compiler-errors:tighten-trait-bound-parsing, r=fmease

2024-06-29T07:14:59+00:00

Move binder and polarity parsing into `parse_generic_ty_bound` Let's pull out the parts of #127054 which just: 1. Make the parsing code less confusing 2. Fix `?use<>` (to correctly be denied) 3. Improve `T: for<'a> 'a` diagnostics This should have no user-facing effects on stable parsing. r? fmease

Move binder and polarity parsing into parse_generic_ty_bound

2024-06-28T23:40:31+00:00