rust/tests/ui/const-generics/defaults, branch try-perf

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: ; | ^^^^^^^^^^^^^^^^^ ```

Fortify generic param default checks

2025-08-05T23:26:26+00:00

expand: Micro-optimize prelude injection

2025-07-28T14:35:09+00:00

Use `splice` to avoid shifting the other items twice. Put `extern crate std;` first so it's already resolved when we resolve `::std::prelude::rust_20XX`.

Add `ty_span` query

2025-07-07T08:13:12+00:00

Rollup merge of #142157 - Enselic:trivial-anon-const-use-cases, r=compiler-errors

2025-06-12T01:14:51+00:00

rustc_resolve: Improve `resolve_const_param_in_non_trivial_anon_const` wording In some contexts, const expressions are OK. Add a `here` to the error message to clarify this. Closes rust-lang/rust#79429 which has 15 x 👍

const-eval error: always say in which item the error occurred

2025-06-07T11:42:30+00:00

also adjust the wording a little so that we don't say "the error occurred here" for two different spans

rustc_resolve: Improve `resolve_const_param_in_non_trivial_anon_const` wording

2025-06-07T11:01:16+00:00

In some contexts, const expressions are OK. Add a `here` to the error message to clarify this.

Clarify why we are talking about a failed const eval at a random place

2025-06-02T15:37:15+00:00

Use the informative error as the main const eval error message

2025-06-02T15:37:15+00:00

compiletest: Make diagnostic kind mandatory on line annotations

2025-04-30T07:44:24+00:00