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.
25 lines
668 B
TOML
25 lines
668 B
TOML
[package]
|
|
name = "rustc_log"
|
|
version = "0.0.0"
|
|
edition = "2024"
|
|
|
|
[dependencies]
|
|
# tidy-alphabetical-start
|
|
tracing = "0.1.28"
|
|
tracing-core = "=0.1.30" # FIXME(Nilstrieb) tracing has a deadlock: https://github.com/tokio-rs/tracing/issues/2635
|
|
tracing-subscriber = { version = "0.3.3", default-features = false, features = ["fmt", "env-filter", "smallvec", "parking_lot", "ansi"] }
|
|
tracing-tree = "0.3.1"
|
|
# tidy-alphabetical-end
|
|
|
|
[dev-dependencies]
|
|
# tidy-alphabetical-start
|
|
rustc_span = { path = "../rustc_span" }
|
|
# tidy-alphabetical-end
|
|
|
|
[features]
|
|
# tidy-alphabetical-start
|
|
max_level_info = ['tracing/max_level_info']
|
|
# tidy-alphabetical-end
|
|
|
|
[lints]
|
|
workspace = true
|