rust/compiler/rustc_parse/src/errors.rs, branch 1.79.0

Revert "Rollup merge of #124099 - voidc:disallow-ambiguous-expr-attrs, r=davidtwco"

2024-06-07T01:12:48+00:00

This reverts commit 57dad1d75e562ff73051c1c43b07eaf65c7dbd74, reversing changes made to 36316df9fe6c3e246153fe6e78967643cf08c148.

Rollup merge of #124218 - Xiretza:subsubdiagnostics, r=davidtwco

2024-04-23T15:25:17+00:00

Allow nesting subdiagnostics in #[derive(Subdiagnostic)]

Rollup merge of #124099 - voidc:disallow-ambiguous-expr-attrs, r=davidtwco

2024-04-23T10:10:26+00:00

Disallow ambiguous attributes on expressions This implements the suggestion in [#15701](https://github.com/rust-lang/rust/issues/15701#issuecomment-2033124217) to disallow ambiguous outer attributes on expressions. This should resolve one of the concerns blocking the stabilization of `stmt_expr_attributes`.

Improve handling of expr->field errors

2024-04-22T15:47:35+00:00

The current message for "`->` used for field access" is the following: ```rust error: expected one of `!`, `.`, `::`, `;`, `?`, `{`, `}`, or an operator, found `->` --> src/main.rs:2:6 | 2 | a->b; | ^^ expected one of 8 possible tokens ``` (playground link[1]) This PR tries to address this by adding a dedicated error message and recovery. The proposed error message is: ``` error: `->` used for field access or method call --> ./tiny_test.rs:2:6 | 2 | a->b; | ^^ help: try using `.` instead | = help: the `.` operator will dereference the value if needed ``` (feel free to bikeshed it as much as necessary) [1]: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=7f8b6f4433aa7866124123575456f54e Signed-off-by: Sasha Pourcelot

Pass translation closure to add_to_diag_with() as reference

2024-04-21T07:45:03+00:00

Disallow ambiguous attributes on expressions

2024-04-18T18:42:19+00:00

Implement `mut ref`/`mut ref mut`

2024-03-27T13:53:23+00:00

Rollup merge of #122120 - fmease:sugg-assoc-ty-bound-on-eq-bound, r=compiler-errors

2024-03-26T20:23:47+00:00

Suggest associated type bounds on problematic associated equality bounds Fixes #105056. TL;DR: Suggest `Trait` on `Trait` in Rust >=2021. ~~Blocked on #122055 (stabilization of `associated_type_bounds`), I'd say.~~ (merged)

Rollup merge of #122217 - estebank:issue-119685, r=fmease

2024-03-24T00:05:51+00:00

Handle str literals written with `'` lexed as lifetime Given `'hello world'` and `'1 str', provide a structured suggestion for a valid string literal: ``` error[E0762]: unterminated character literal --> $DIR/lex-bad-str-literal-as-char-3.rs:2:26 | LL | println!('hello world'); | ^^^^ | help: if you meant to write a `str` literal, use double quotes | LL | println!("hello world"); | ~ ~ ``` ``` error[E0762]: unterminated character literal --> $DIR/lex-bad-str-literal-as-char-1.rs:2:20 | LL | println!('1 + 1'); | ^^^^ | help: if you meant to write a `str` literal, use double quotes | LL | println!("1 + 1"); | ~ ~ ``` Fix #119685.

Suggest assoc ty bound on lifetime in eq constraint

2024-03-22T23:17:30+00:00