No way to allow an unknown lint on the command line #81906
Labels
A-driver
Area: rustc_driver that ties everything together into the `rustc` compiler
C-bug
Category: This is a bug.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
When migrating a large codebase to a new compiler version, frequently there are new lints. In codebases that enable
-Dwarnings
, this causes a problem: we'd like to allow the new lint temporarily before fixing in-tree, but passing-Anew-lint-here
to the old compiler gives us an error. If we can't upgrade the compiler and build flags in lock step, we are stuck.-Aunknown-lints
exists, but does not have the desired effect on the command line:Since the same problem that
unknown-lints
solves exists on the command line, I'd argue that this is a bug in the CLI.As a corollary, it would be nice if we could do something like
-Aunknown-lints -Alegacy-derive-helpers -Dunknown-lints
to prevent misspellings elsewhere in the command line.The text was updated successfully, but these errors were encountered: