cargo-udeps VS arewefastyet

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...

That page averages all the builds across different code bases. It doesn’t specify which version/tag of which code base, nor does it talk about the hardware.

https://arewefastyet.pages.dev/ - This page tracks compile times across some common crates over all supported compiler versions, with different hardware (2, 4, 8, 16 cores). This used to be https://arewefastyet.rs but the domain expired.

https://arewefastyet.rs/ see benchmark

You can check incremental compile times on http://arewefastyet.rs. Choose one compile mode (Debug OR Release, preferably Debug), one hardware config (4 cores let's say) and both profile modes (Clean, Incremental).

Compile times in rustc have been steadily improving with time, as shown here - https://arewefastyet.rs.

Every release doesn't make every workload faster, but over a long time horizon, the effect is clear. Rust 1.34 was released in April 2019 and since then many crates have become 33-50% faster to compile, depending on the hardware and the compiler mode (clean/incremental, check/debug/release).

Interestingly, the speedup mentioned in OP won't show up in these charts because that's a change on macOS and these benchmarks were recorded on Linux.

What is expected to be a gamechanger is the release of cranelift in 2021 or 2022. It's an alternate debug backend that promises much faster debug builds.

Yes plenty of effort goes into making Rust compilation faster, see https://arewefastyet.rs/, its FAQ, and some easy internet searches.

Thanks for your work on arewefastyet.rs, I was about to post a link to it haha

I implemented something similar. Deserialising a comma separated strings into a struct - example. Hope that helps!