Closed tommy-gilligan closed 1 year ago
I've cherry-picked these fixes, but I've decided not to enforce them on GitHub Actions -- for a project with only sporadic contributions, that's just setting up the next new contributor to run into new warnings introduced by a new clippy version failing their build. Clippy is great as a warning, but I don't think we should block on it because it makes things into breaking changes that don't need to be.
Run
cargo clippy
andcargo fmt
on CI. I've run these locally and then gotten them to pass. This also adds--all-features
in a few spots to ensure the example binaries are getting built on CI.