rust/compiler/rustc_ast_ir/src, branch master

turn pointer width into an integer in target.json

2025-08-27T21:44:49+00:00

Deduplicate `IntTy`/`UintTy`/`FloatTy`.

2025-07-31T09:56:11+00:00

There are identical definitions in `rustc_type_ir` and `rustc_ast`. This commit removes them and places a single definition in `rustc_ast_ir`. This requires adding `rust_span` as a dependency of `rustc_ast_ir`, but means a bunch of silly conversion functions can be removed. The one annoying wrinkle is that the old version had differences in their `Debug` impls, e.g. one printed `u32` while the other printed `U32`. Some compiler error messages rely on the former (yuk), and some clippy output depends on the latter. So the commit also changes clippy to not rely on `Debug` and just implement what it needs itself.

Use {Decodable,Encodable}_NoContext in type_ir

2025-03-15T06:34:36+00:00

Remove `#![warn(unreachable_pub)]` from all `compiler/` crates.

2025-03-11T02:14:21+00:00

It's no longer necessary now that `-Wunreachable_pub` is being passed.

Revert "Use workspace lints for crates in `compiler/` #138084"

2025-03-10T10:12:47+00:00

Revert to buy time to consider options that avoids breaking downstream usages of cargo on distributed `rustc-src` artifacts, where such cargo invocations fail due to inability to inherit `lints` from workspace root manifest's `workspace.lints` (this is only valid for the source rust-lang/rust workspace, but not really the distributed `rustc-src` artifacts). This breakage was reported in . This reverts commit 48caf81484b50dca5a5cebb614899a3df81ca898, reversing changes made to c6662879b27f5161e95f39395e3c9513a7b97028.

Remove `#![warn(unreachable_pub)]` from all `compiler/` crates.

2025-03-07T21:41:43+00:00

(Except for `rustc_codegen_cranelift`.) It's no longer necessary now that `unreachable_pub` is in the workspace lints.

Make fewer crates depend on rustc_ast_ir

2025-02-19T07:06:54+00:00

Add sugar for &pin (const|mut) types

2024-10-07T18:15:04+00:00

Add `warn(unreachable_pub)` to several crates.

2024-08-15T22:46:13+00:00

It requires no additonal changes to these crates, but will prevent unnecessary `pub`s in the future.

Use `tidy` to sort crate attributes for all compiler crates.

2024-06-12T05:49:10+00:00

We already do this for a number of crates, e.g. `rustc_middle`, `rustc_span`, `rustc_metadata`, `rustc_span`, `rustc_errors`. For the ones we don't, in many cases the attributes are a mess. - There is no consistency about order of attribute kinds (e.g. `allow`/`deny`/`feature`). - Within attribute kind groups (e.g. the `feature` attributes), sometimes the order is alphabetical, and sometimes there is no particular order. - Sometimes the attributes of a particular kind aren't even grouped all together, e.g. there might be a `feature`, then an `allow`, then another `feature`. This commit extends the existing sorting to all compiler crates, increasing consistency. If any new attribute line is added there is now only one place it can go -- no need for arbitrary decisions. Exceptions: - `rustc_log`, `rustc_next_trait_solver` and `rustc_type_ir_macros`, because they have no crate attributes. - `rustc_codegen_gcc`, because it's quasi-external to rustc (e.g. it's ignored in `rustfmt.toml`).