cargo-sweep
A cargo subcommand for cleaning up unused build files generated by Cargo (by holmgr)
bacon
background rust code check (by Canop)
| cargo-sweep | bacon | |
|---|---|---|
| 9 | 25 | |
| 680 | 1,463 | |
| - | - | |
| 6.6 | 8.0 | |
| about 2 months ago | 9 days ago | |
| Rust | Rust | |
| MIT License | GNU Affero General Public License v3.0 |
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.
cargo-sweep
Posts with mentions or reviews of cargo-sweep.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-08.
-
Target file are very huge and running out of storage on mac.
You can use cargo sweep or kondo to clean up unused files.
-
What are some useful tools for Rust?
cargo-sweep
-
crates.io now has more than 100,000 crates!
[1]: https://github.com/holmgr/cargo-sweep
-
Cargo Clean All - A cargo plugin to clean all your projects at once with filters
I use https://github.com/holmgr/cargo-sweep which can keep files from the current compiler version, but delete files from earlier compilers that won't ever be used again.
-
Announcing cargo-cleanall
How is this different from https://github.com/holmgr/cargo-sweep ?
-
Is this normal? Giant debug folder
I like https://github.com/holmgr/cargo-sweep to keep the size of /target from unbounded growth without fully losing the useful portion of the cache. It's the same outcome as Cargo clean after a reboot but I recently also started using a ramdisk with CARGO_TARGET_DIR. Much easier to do on Linux.
- Cargo clean for a number of projects
-
Blog Post: Fast Rust Builds
cargo-sweep can do this kind of garbage collection along a few axes - rustc version, file age, was or wasn't used during recent build. Works great on Linux. I've not gotten it working reliably for -s/-f on MacOS+APFS, but for the CI use case it should be a nice improvement.
-
STOP DOING RUST
holmgr is a god and cargo-sweep is a godsend
bacon
Posts with mentions or reviews of bacon.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-27.
- Bacon – a background Rust code checker
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
Probably one of the biggest speed ups to your inner loop writing / running code is to use something like https://github.com/Canop/bacon/. I used a combination of the docs and GPT chats to increase my learning speed a lot.
-
Project Diagnostics
Nice, I'll have a look. I miss having bacon in a tmux split, wish TS had something like that.
-
Report on platform-compliance for cargo directories
As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.
-
What's your current Vim+Rust setup?
bacon + nvim-bacon
-
What are some useful tools for Rust?
bacon
-
Are there any continuous testing tools with real-time line-by-line IDE feedback for Rust?
I love cargo-watch and still it use it situationally, but as a companion to my editor workflow I mostly switched to bacon. Being able to switch with one keystroke to another cargo subcommand is delightful.
-
What is your number one rust tool?
Try bacon for checks & test!
-
Alternative to watch -cq
Was it bacon perhaps?
- Something similar to Rust's `bacon` tool but for Python?
What are some alternatives?
When comparing cargo-sweep and bacon you can also consider the following projects:
cargo-chef - A cargo-subcommand to speed up Rust Docker builds using Docker layer caching.
rust - Empowering everyone to build reliable and efficient software.
rules_rust - Rust rules for Bazel
cargo-geiger - Detects usage of unsafe Rust in a Rust crate and its dependencies.
cargo-clean-all
helix - A post-modern modal text editor.
kondo - Cleans dependencies and build artifacts from your projects.
miri - An interpreter for Rust's mid-level intermediate representation
squatternaut - A snapshot of name squatting on crates.io
darkfi - Anonymous. Uncensored. Sovereign.
cargo-hack - Cargo subcommand to provide various options useful for testing and continuous integration.
config - configuration.nix is better than dot files