Closed sboeuf closed 1 year ago
/cc @rbradford I think this is fixing #309 :)
/cc @rbradford I think this is fixing #309 :)
Although this is definitely an improvement - catching errors in the test build. I don't think it is the equivalent of cargo clippy --tests
as this make clippy cover the test code?
/cc @rbradford I think this is fixing #309 :)
Although this is definitely an improvement - catching errors in the test build. I don't think it is the equivalent of
cargo clippy --tests
as this make clippy cover the test code?
Well I know this is different but this is eventually reaching the same goal of "not allowing warnings to be missed".
/cc @rbradford I think this is fixing #309 :)
Although this is definitely an improvement - catching errors in the test build. I don't think it is the equivalent of
cargo clippy --tests
as this make clippy cover the test code?Well I know this is different but this is eventually reaching the same goal of "not allowing warnings to be missed".
This is definitely an improvement but it doesn't solve #309 which is about clippy not covering the tests as clippy warns about things that rustc doesn't.
Thanks, I merged this, then reopened 309.
Turn on the rustc flag
-Dwarnings
for all bazel rust tests so that all warnings would show up as errors.Fixes #309