rust/tests/ui/span, branch perf-tmp

indexing: reword help

2025-10-01T07:39:03+00:00

Co-authored-by: beef

use `try_structurally_resolve_type` for method receiver

2025-09-26T14:33:15+00:00

We'll still error due to the `opt_bad_ty` of `method_autoderef_steps`. This slightly worsens the span of `infer_var.method()` which is now the same as for `Box::new(infer_var).method()`. Unlike `structurally_resolve_type`, `probe_op` does not check whether the infcx is already tainted, so this results in 2 previously not emitted errors.

On binding not present in all patterns, suggest potential typo

2025-08-25T15:16:25+00:00

``` error[E0408]: variable `Ban` is not bound in all patterns --> f12.rs:9:9 | 9 | (Foo,Bar)|(Ban,Foo) => {} | ^^^^^^^^^ --- variable not in all patterns | | | pattern doesn't bind `Ban` | help: you might have meant to use the similarly named previously used binding `Bar` | 9 - (Foo,Bar)|(Ban,Foo) => {} 9 + (Foo,Bar)|(Bar,Foo) => {} | ```

On E0277, point at type that doesn't implement bound

2025-08-22T17:55:15+00:00

When encountering an unmet trait bound, point at local type that doesn't implement the trait: ``` error[E0277]: the trait bound `Bar: Foo` is not satisfied --> $DIR/issue-64855.rs:9:19 | LL | pub struct Bar(::Type) where Self: ; | ^^^^^^^^^^^^^^^^^^^ unsatisfied trait bound | help: the trait `Foo` is not implemented for `Bar` --> $DIR/issue-64855.rs:9:1 | LL | pub struct Bar(::Type) where Self: ; | ^^^^^^^^^^^^^^^^^ ```

bless tests with new lint messages

2025-08-19T19:27:10+00:00

Rollup merge of #145378 - xizheyin:144968, r=davidtwco

2025-08-15T06:16:41+00:00

Add `FnContext` in parser for diagnostic Fixes rust-lang/rust#144968 Inspired by https://github.com/rust-lang/rust/issues/144968#issuecomment-3156094581, I implemented `FnContext` to indicate whether a function should have a self parameter, for example, whether the function is a trait method, whether it is in an impl block. And I removed the outdated note. I made two commits to show the difference. cc ``@estebank`` ``@djc`` r? compiler

Adjust error message grammar to be less awkward

2025-08-14T16:50:07+00:00

Add FnContext in parser for diagnostic

2025-08-14T13:31:47+00:00

Signed-off-by: xizheyin

Add more docs to templates for attrs with incorrect arguments

2025-08-11T17:02:32+00:00

Allow attr entries to declare list of alternatives for `List` and `NamedValueStr`

2025-08-11T16:00:49+00:00

Modify `AttributeTemplate` to support list of alternatives for list and name value attribute styles. Suggestions now provide more correct suggested code: ``` error[E0805]: malformed `used` attribute input --> $DIR/used_with_multi_args.rs:3:1 | LL | #[used(compiler, linker)] | ^^^^^^------------------^ | | | expected a single argument here | help: try changing it to one of the following valid forms of the attribute | LL - #[used(compiler, linker)] LL + #[used(compiler)] | LL - #[used(compiler, linker)] LL + #[used(linker)] | LL - #[used(compiler, linker)] LL + #[used] | ``` instead of the prior "masking" of the lack of this feature by suggesting pipe-separated lists: ``` error[E0805]: malformed `used` attribute input --> $DIR/used_with_multi_args.rs:3:1 | LL | #[used(compiler, linker)] | ^^^^^^------------------^ | | | expected a single argument here | help: try changing it to one of the following valid forms of the attribute | LL - #[used(compiler, linker)] LL + #[used(compiler|linker)] | LL - #[used(compiler, linker)] LL + #[used] | ```