measureme
cargo-udeps
| measureme | cargo-udeps | |
|---|---|---|
| 2 | 6 | |
| 323 | 1,538 | |
| 1.5% | - | |
| 7.2 | 8.5 | |
| about 2 months ago | 16 days ago | |
| Rust | Rust | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
measureme
-
1.56 Compile time is through the roof!?
To dig further into one specific rustc process called by Cargo, cargo +nightly rustc -- -Z self-profile -p some_crate https://github.com/rust-lang/measureme/blob/master/summarize/README.md
-
Reducing Rust Incremental Compilation Times on macOS by 70%
> When does the Rust compiler spend most of it's time? Is it at the checking stage?
rustc has a self-profiler that can be used to answer this question [0], as well as a mode that times each compiler pass [1].
There's no single reason the Rust compiler is slow, as it depends quite heavily on the code being compiled. For some codebases, LLVM code takes up most of the time; in other codebases (e.g., extremely generic-heavy codebases), it'll be checking-related passes.
[0]: https://github.com/rust-lang/measureme/blob/master/summarize...
[1]: https://wiki.alopex.li/WhereRustcSpendsItsTime
cargo-udeps
-
cargo-udeps 0.1.33 release
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.
-
Why can rust-analyzer not detect unused dependencies?
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).
- Is there a tool to remove unused dependencies from a Cargo file?
-
Is the crate dependency becoming a problem?
Maybe an extension to cargo-udeps?
-
Corrode without bloat. Is detecting unnecessary features feasible?
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.
-
Reducing Rust Incremental Compilation Times on macOS by 70%
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...
What are some alternatives?
cargo-llvm-lines - Count lines of LLVM IR per generic function
cargo-machete - Remove unused Rust dependencies with this one weird trick!
arewefastyet - arewefastyet.rs - benchmarking the Rust compiler
bmrng - An async MPSC request-response channel for Tokio
cargo-bisect-rustc - Bisects rustc, either nightlies or CI artifacts
mold - Mold: A Modern Linker ðŸ¦
scip - SCIP Code Intelligence Protocol
cargo-dephell - Cargo dephell analyzes the third-party dependencies of a Rust workspace
dmd - dmd D Programming Language compiler
whackadep - Managing Rust dependencies via a dashboard
Cargo - The Rust package manager