rust/compiler/rustc_errors/src/diagnostic_impls.rs, branch beta

Move `IntoDiagArg` earlier in the dependency chains

2025-08-20T22:01:13+00:00

`rustc_errors` depends on numerous crates, solely to implement its `IntoDiagArg` trait on types from those crates. Many crates depend on `rustc_errors`, and it's on the critical path. We can't swap things around to make all of those crates depend on `rustc_errors` instead, because `rustc_errors` would end up in dependency cycles. Instead, move `IntoDiagArg` into `rustc_error_messages`, which has far fewer dependencies, and then have most of these crates depend on `rustc_error_messages`. This allows `rustc_errors` to drop dependencies on several crates, including the large `rustc_target`. (This doesn't fully reduce dependency chains yet, as `rustc_errors` still depends on `rustc_hir` which depends on `rustc_target`. That will get fixed in a subsequent commit.)

Port `#[custom_mir(..)]` to the new attribute system

2025-08-15T09:19:29+00:00

remove rustc_attr_data_structures

2025-07-31T12:19:27+00:00

compiler: Parse `p-` specs in datalayout string, allow definition of custom default data address space

2025-07-07T07:04:53+00:00

Move eager translation to a method on `Diag`

2025-04-17T01:38:59+00:00

This will allow us to eagerly translate messages on a top-level diagnostic, such as a `LintDiagnostic`. As a bonus, we can remove the awkward closure passed into Subdiagnostic and make better use of `Into`.

Fix rebase

2025-02-25T17:27:22+00:00

Teach structured errors to display short `Ty`

2025-02-25T16:56:03+00:00

Make it so that every structured error annotated with `#[derive(Diagnostic)]` that has a field of type `Ty<'_>`, the printing of that value into a `String` will look at the thread-local storage `TyCtxt` in order to shorten to a length appropriate with the terminal width. When this happen, the resulting error will have a note with the file where the full type name was written to. ``` error[E0618]: expected function, found `((..., ..., ..., ...), ..., ..., ...)`` --> long.rs:7:5 | 6 | fn foo(x: D) { //~ `x` has type `(... | - `x` has type `((..., ..., ..., ...), ..., ..., ...)` 7 | x(); //~ ERROR expected function, found `(... | ^-- | | | call expression requires function | = note: the full name for the type has been written to 'long.long-type-14182675702747116984.txt' = note: consider using `--verbose` to print the full type name to the console ```

Introduce new-style attribute parsers for several attributes

2025-02-24T13:31:17+00:00

note: compiler compiles but librustdoc and clippy don't

compiler: replace ExternAbi::name calls with formatters

2025-02-12T03:42:47+00:00

Most of these just format the ABI string, so... just format ExternAbi? This makes it more consistent and less jank when we can do it.

Simplify intra-crate qualifiers.

2025-02-11T03:59:13+00:00

The following is a weird pattern for a file within `rustc_middle`: ``` use rustc_middle::aaa; use crate::bbb; ``` More sensible and standard would be this: ``` use crate::{aaa, bbb}; ``` I.e. we generally prefer using `crate::` to using a crate's own name. (Exceptions are things like in macros where `crate::` doesn't work because the macro is used in multiple crates.) This commit fixes a bunch of these weird qualifiers.