rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-03-10	Revert "Use workspace lints for crates in `compiler/` #138084"	许杰友 Jieyou Xu (Joe)	-3/+0
	Revert <https://github.com/rust-lang/rust/pull/138084> 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 <https://github.com/rust-lang/rust/issues/138304>. This reverts commit 48caf81484b50dca5a5cebb614899a3df81ca898, reversing changes made to c6662879b27f5161e95f39395e3c9513a7b97028.
2025-03-08	Specify rust lints for `compiler/` crates via Cargo.	Nicholas Nethercote	-0/+3
	By naming them in `[workspace.lints.rust]` in the top-level `Cargo.toml`, and then making all `compiler/` crates inherit them with `[lints] workspace = true`. (I omitted `rustc_codegen_{cranelift,gcc}`, because they're a bit different.) The advantages of this over the current approach: - It uses a standard Cargo feature, rather than special handling in bootstrap. So, easier to understand, and less likely to get accidentally broken in the future. - It works for proc macro crates. It's a shame it doesn't work for rustc-specific lints, as the comments explain.
2025-02-22	Upgrade the compiler to edition 2024	Michael Goulet	-1/+1

2025-02-16	Move hashes from rustc_data_structure to rustc_hashes so they can be shared ↵	Ben Kimock	-0/+140
	with rust-analyzer