Use .cargo/config.toml for local compilation options

This will be ignored when Clippy is part of the compiler workspace.
Using `Cargo.toml` would complain about profiles defined outside the
top-level when run from the compiler repository.
This commit is contained in:
Samuel Tardieu 2025-08-23 10:31:38 +02:00
parent 55286e796f
commit 2c28135116
No known key found for this signature in database
GPG key ID: BDDC3208C6FEAFA8
2 changed files with 7 additions and 7 deletions

View file

@ -23,3 +23,10 @@ split-debuginfo = "unpacked"
rustflags = ["--remap-path-prefix", "=clippy_dev"]
[profile.dev.package.lintcheck]
rustflags = ["--remap-path-prefix", "=lintcheck"]
# quine-mc_cluskey makes up a significant part of the runtime in dogfood
# due to the number of conditions in the clippy_lints crate
# and enabling optimizations for that specific dependency helps a bit
# without increasing total build times.
[profile.dev.package.quine-mc_cluskey]
opt-level = 3

View file

@ -65,13 +65,6 @@ harness = false
name = "dogfood"
harness = false
# quine-mc_cluskey makes up a significant part of the runtime in dogfood
# due to the number of conditions in the clippy_lints crate
# and enabling optimizations for that specific dependency helps a bit
# without increasing total build times.
[profile.dev.package.quine-mc_cluskey]
opt-level = 3
[lints.rust.unexpected_cfgs]
level = "warn"
check-cfg = ['cfg(bootstrap)']