Open jinohkang-theori opened 6 months ago
Thanks for the report.
I guess this is a matter of fact that cargo fix
runs cargo check
under the hood to get the JSON diagnostics from rustc. Hence, the result of cargo check
is cached.
It might be tricky to fix this, as Cargo might need to distinguish caches between fix
and check
. Doing so would need to wipe out the entire caches, which is pretty undesired. For now I might recommend scoping cargo clean
with --package
or --target
or other flags, so we can clean part of the cache without rebuild from the beginning.
Problem
After
cargo fix
emits warnings, subsequentcargo check
commands with the same arguments will not emit an error despite existence of-D
flag, until the build cache is cleared.Steps
Possible Solution(s)
No response
Notes
This looks like it's caused by forced demotion of errors into warnings in fix mode, which pollutes the result cache for
cargo check
.Version