Closed sboeuf closed 1 year ago
hm, why didn't CI catch this?
hm, why didn't CI catch this?
Yeah that's a shame it didn't. That's because we need to pass some extra flags to bazel clippy if we want warnings to be treated as errors. Fingers crossed this is something bazel supports.
We seem to have lost check for warnings in the move to bazel?
Sorry, passed my usual pre-commit tests because no errors were raised.
We seem to have lost check for warnings in the move to bazel?
Sorry, passed my usual pre-commit tests because no errors were raised.
No worries at all, I really hope we can find out how to re-enable this treat warnings as errors
in bazel.
Resolves following clippy warning: