whackadep VS cargo-udeps

Checkout whackadep if you’re really interested in this! https://github.com/diem/whackadep

That's why I started https://github.com/mimoo/cargo-dephell and https://github.com/diem/whackadep btw, to try to get a sense of the risk in our Rust dependencies. The second one is a web UI that can update periodically and shows you what's up with your dependencies. If there's a new update, it'll tell you if it affected a `build.rs` file (which triggers a warning). I wanted to add more rules, like the ones mentioned in the article, but never had the time to do it.

Check whackadep and cargo-dephell: https://github.com/mimoo/cargo-dephell and https://github.com/diem/whackadep

I'm releasing cargo-udeps 0.1.33 today. The release marks a big change in the evolution of cargo-udeps, as the default backend is changed from using save-analysis to depinfo. This change was needed because the compiler is removing support for save-analysis. I will remove support for the save-analysis backend entirely in a couple of weeks, when the 1.64 release is made, and I'll update cargo-udeps to the new cargo release.

rust-analyzer only provides a handful of diagnostics by itself, everything else is forwarded from cargo check (if checkOnSave is enabled). Neither tool currently emits a warning for unused dependencies, since it's pretty hard to do, but cargo-udeps can do it (though I'm not sure how reliable it is).

Maybe an extension to cargo-udeps?

cargo-udeps does a great job at letting us know which dependencies in our `Cargo.toml` are left unused. I am pretty impressed with it.

You can also turn off debuginfo completely. Personally, someone who does printf debugging, I mainly need it to debug segfaults, which are really rare in Rust. Sometimes the call stack of a panic is useful as well, but if I need debuginfo I can just re-enable it.

https://github.com/est31/cargo-udeps/commit/e550d93c7a6d756e...