cargo careful: run your Rust code with extra careful debug checking
Did you know that the standard library is full of useful checks that users never get to see? There are plenty of debug assertions in the standard library that will do things like check that char::from_u32_unchecked is called on a valid char, that CStr::from_bytes_with_nul_unchecked does not have internal nul bytes, or that pointer functions such as copy or copy_nonoverlapping are called on suitably aligned non-null (and non-overlapping) pointers. However, the regular standard library that is distributed by rustup is compiled without debug assertions, so there is no easy way for users to benefit from all this extra checking.
cargo careful is here to close this gap: when invoked the first time, it builds a standard library with debug assertions from source, and then runs your program or test suite with that standard library. Installing cargo careful is as easy as cargo install cargo-careful, and then you can do cargo +nightly careful run/cargo +nightly careful test to execute your binary crates and test suites with an extra amount of debug checking.
This will naturally be slower than a regular debug or release build, but it is much faster than executing your program in Miri and still helps find some Undefined Behavior. Unlike Miri, it is fully FFI-compatible (though the code behind the FFI barrier is completely unchecked). Of course Miri is much more thorough and cargo careful will miss many problems (for instance, it cannot detect out-of-bounds pointer arithmetic – but it does perform bounds checking on get_unchecked slice accesses).
