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.
19 lines
503 B
TOML
19 lines
503 B
TOML
[package]
|
|
name = "rustc_attr_data_structures"
|
|
version = "0.0.0"
|
|
edition = "2024"
|
|
|
|
[dependencies]
|
|
# tidy-alphabetical-start
|
|
rustc_abi = {path = "../rustc_abi"}
|
|
rustc_ast = {path = "../rustc_ast"}
|
|
rustc_ast_pretty = {path = "../rustc_ast_pretty"}
|
|
rustc_data_structures = {path = "../rustc_data_structures"}
|
|
rustc_macros = {path = "../rustc_macros"}
|
|
rustc_serialize = {path = "../rustc_serialize"}
|
|
rustc_span = {path = "../rustc_span"}
|
|
thin-vec = "0.2.12"
|
|
# tidy-alphabetical-end
|
|
|
|
[lints]
|
|
workspace = true
|