Thank you for the suggestions and code review via blog post ;)
You are correct that `#[deny]` is what I want with Clippy.
The env_logger builder is something I didn't know about. The homepage for the docs does not even mention it - https://docs.rs/env_logger/0.6.0/env_logger/. I agree that I should depend on my own env variable, but should cargo not do the same?
Well cargo and rustc are both first-party Rust tools, so it's expected that they would use "RUST_LOG". I have wondered why env_logger defaults to using it instead of requiring you to specify which env var you want to parse, but it is what it is.
You are correct that `#[deny]` is what I want with Clippy.
The env_logger builder is something I didn't know about. The homepage for the docs does not even mention it - https://docs.rs/env_logger/0.6.0/env_logger/. I agree that I should depend on my own env variable, but should cargo not do the same?