Using cargo clippy -- -Wclippy::pedantic to find some further low hanging fruit.
The false positive rate is quite high, so I'm tempted to include some line allows like
#![allow(cargo::range_plus_one)]
However I'm not sure you would agree that it is a good idea since the default cargo clippy does not complain.
One compromise would be to have it enabled in a separate branch like pedantic or dev where we could use to merge recent fixes to look through the course in a strict(pedantic), yet context aware(we know some are false positives) way.
I've checked it with -Wclippy::pedantic. TBH it looks like very excessive = a lot of work for nothing.
However, we can enable this mode if you prepare the branch without warnings.
Using
cargo clippy -- -Wclippy::pedantic
to find some further low hanging fruit. The false positive rate is quite high, so I'm tempted to include some line allows like#![allow(cargo::range_plus_one)]
However I'm not sure you would agree that it is a good idea since the default
cargo clippy
does not complain. One compromise would be to have it enabled in a separate branch likepedantic
ordev
where we could use to merge recent fixes to look through the course in a strict(pedantic), yet context aware(we know some are false positives) way.