beba32cebb
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.
20 lines
587 B
TOML
20 lines
587 B
TOML
[package]
|
|
name = "rustc_lint_defs"
|
|
version = "0.0.0"
|
|
edition = "2024"
|
|
|
|
[dependencies]
|
|
# tidy-alphabetical-start
|
|
rustc_abi = { path = "../rustc_abi" }
|
|
rustc_ast = { path = "../rustc_ast" }
|
|
rustc_data_structures = { path = "../rustc_data_structures" }
|
|
rustc_error_messages = { path = "../rustc_error_messages" }
|
|
rustc_hir = { path = "../rustc_hir" }
|
|
rustc_macros = { path = "../rustc_macros" }
|
|
rustc_serialize = { path = "../rustc_serialize" }
|
|
rustc_span = { path = "../rustc_span" }
|
|
serde = { version = "1.0.125", features = ["derive"] }
|
|
# tidy-alphabetical-end
|
|
|
|
[lints]
|
|
workspace = true
|