bmrng
An async MPSC request-response channel for Tokio (by oguzbilgener)
cargo-udeps
Find unused dependencies in Cargo.toml (by est31)
| bmrng | cargo-udeps | |
|---|---|---|
| 1 | 6 | |
| 11 | 1,538 | |
| - | - | |
| 0.0 | 8.5 | |
| over 1 year ago | 17 days ago | |
| Rust | Rust | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
bmrng
Posts with mentions or reviews of bmrng.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-09.
-
Is the crate dependency becoming a problem?
This was exactly what I did to shave a full minute off CI build times (from 3 minutes to 2 minutes) in one of the projects I depended on. However, rather than just removing default-features, I replaced the futures crate entirely with its significantly lightweight sub-crate futures-core when I realized that the project only ever used futures for the Stream trait.
cargo-udeps
Posts with mentions or reviews of cargo-udeps.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-15.
-
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?
When comparing bmrng and cargo-udeps you can also consider the following projects:
cargo-dephell - Cargo dephell analyzes the third-party dependencies of a Rust workspace
cargo-machete - Remove unused Rust dependencies with this one weird trick!