If I have some code that raises an allow-by-default lint:
fn foo(s: &str) {
dbg!(s); // would raise `dbg_macro`
}and run Clippy with that lint explicitly enabled:
cargo clippy -- -W clippy::dbg_macro
then I get the following output:
warning: the `dbg!` macro is intended as a debugging tool
--> src/main.rs:3:5
|
3 | dbg!(s);
| ^^^^^^^
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.92.0/index.html#dbg_macro
= note: requested on the command line with `-W clippy::dbg-macro`
help: remove the invocation before committing it to a version control system
|
3 - dbg!(s);
3 + s;
|
warning: `tst` (bin "tst") generated 1 warning (run `cargo clippy --fix --bin "tst" -p tst` to apply 1 suggestion)
but running the suggested command (cargo clippy --fix --bin "tst" -p tst) won't actually apply the suggestion, as Clippy won't even think about linting on dbg!() -- what's needed is cargo clippy --fix --bin "tst" -p tst -- -W clippy::dbg_macro
If I have some code that raises an allow-by-default lint:
and run Clippy with that lint explicitly enabled:
then I get the following output:
but running the suggested command (
cargo clippy --fix --bin "tst" -p tst) won't actually apply the suggestion, as Clippy won't even think about linting ondbg!()-- what's needed iscargo clippy --fix --bin "tst" -p tst -- -W clippy::dbg_macro