Hi all, just musing - what tools do you use during dev/CI for static analysis and ensuring quality/consistency?
I'll start with the obvious ones:
Shout out to arbitrary and arbtest for generating sample data in tests
What other "necessary" tools/libs do you use to improve quality in Rust?
Miri can (and probably should) be used for raising the confidence in unsafe code. (I am intentionally not writing "ensure correctness", because nothing but a formal proof by a human can achieve that.)
If we include benchmarking here, Criterion seems to be a de-facto standard way to do this better then the default.
In Tokio, we use the following tools:
cargo check or cargo test on many different platformscargo update -Z minimal-versions to test that the oldest allowed version of each dependency has everything we needcargo check on our MSRV.I've managed to avoid unsafe and plan to continue doing so :-). I know my limits 
excellent - thanks. I love the idea of idea of running it with the latest rustup update and cargo update too.
cargo fuzz makes it easy to write fuzz tests. The popular understanding of fuzzing is that it is for finding memory safety bugs in parsers, but it is also capable of finding other kinds of edge-case situations — I use it to check that my algorithms do not panic, hang, OOM, or produce obvious nonsense when given arbitrary numbers as input.
Run fuzzing in CI as a scheduled or non-required job so you're not personally waiting for it all the time.