rust - Difference Between `cargo clippy --all --fix --allow-dirty --allow-staged` and `cargo clippy --all --tests -- -D warnings

Executing cargo clippy --all --fix --allow-dirty --allow-staged will automatically fix the code, but if you don't execute it, meaning you don't fix those codes, cargo clippy --all --tests -- -D warnings can pass.

Is there a difference in how the former and the latter handle the rules?

I tried looking through various documents and source code but couldn't find the answer.

I guess it's because of different scanning ranges or rule requirements, but I don't have any documentation or evidence of clip source code.

Executing cargo clippy --all --fix --allow-dirty --allow-staged will automatically fix the code, but if you don't execute it, meaning you don't fix those codes, cargo clippy --all --tests -- -D warnings can pass.

Is there a difference in how the former and the latter handle the rules?

I tried looking through various documents and source code but couldn't find the answer.

I guess it's because of different scanning ranges or rule requirements, but I don't have any documentation or evidence of clip source code.

• rust
• rust-cargo
• rust-clippy

Share Improve this question Follow edited Jan 17 at 19:12 heygsc asked Jan 17 at 18:31 heygscheygsc 11077 bronze badges 3

• Can you provide an example? – kmdreko Commented Jan 17 at 19:00
• I meant can you provide a minimal reproducible example? Take one of the changes you're seeing and minimize it to only the code required to demonstrate it. Your examples are not trivial. – kmdreko Commented Jan 17 at 19:12
• It doesn't seem easy. It is known that the changes came from the examples folder, but it cannot be completely ruled out whether it was due to specific rules or the scope of the folder. Perhaps it is best to be able to clearly distinguish the difference from the command:) – heygsc Commented Jan 17 at 19:14

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

From the Clippy documentation:

Clippy can automatically apply some lint suggestions, just like the compiler. Note that --fix implies --all-targets, so it can fix as much code as it can.

Thus, in order to get the same behavior without --fix, you should pass the --all-targets option.

You should also not use the --tests option, because that is a narrower target filter than --all-targets — it selects all targets that are tested by default; fromthe Target Selection section of the similar cargo check command:

Check all targets that have the test = true manifest flag set. By default this includes the library and binaries built as unittests, and integration tests.

Note that this set does not include examples. So, your command cargo clippy --all --tests -- -D warnings will fail only if Clippy finds a warning or error in any of your tested-by-default targets, and all other targets, including examples, are not checked at all.

--all-targets --tests is in practice equivalent to just --all-targets, but the --tests part is redundant, so you should leave it out.