cargo-sweep
cargo-sweep copied to clipboard
holmgr
A cargo subcommand for cleaning up unused build files generated by Cargo
``` $ cargo run -- sweep --file ``` ``` thread 'main' panicked at src/main.rs:237:18: Failed to load timestamp file: failed to read stamp file /home/marcospb19/cargo-sweep/sweep.timestamp Caused by: No such file...
``` $ cargo sweep -r -t 30 -i error: The argument '--time ' cannot be used with one or more of the other specified arguments USAGE: cargo-sweep sweep -r For...
Whenever I use cargo-sweep, the rust-analyzer takes a lot of time to finish its analysis. Is there a way to skip deleting those files?
There are debug and incremental artifacts remaining. They are older than `-t 0` ``` quickwit git:(main) cargo sweep -r -t 0 [INFO] Cleaned 5.27 GiB from "/home/pascal/LinuxData/Development/quickwit/agg_error/quickwit/target" [INFO] Cleaned 5.44...
This would allow cleaning of e.g. a project you mostly work with productively but you compile it in debug mode occasionally to fix some bugs or add small features. The...
I'm getting this error when running `cargo sweep` on Ubuntu 23.04: ``` [INFO] Using all installed toolchains: ["stable-x86_64-unknown-linux-gnu", "stable-x86_64-unknown-linux-musl"] [ERROR] Failed to clean "/home/fenhl/wslgit/github.com/midoshouse/rust-ootr-utils/target" Caused by: failed to determine fingerprint...
## Current behavior With the exception of this metadata error that usually occurs when you're not running inside a project: https://github.com/holmgr/cargo-sweep/blob/475ac9ec16518596fc21cb2ea77bd8045b5a4a6d/src/main.rs#L154-L157 For every possible error in `cargo-sweep`, it reports the...
I think it would be a good small improvement if `cargo-sweep` emitted a different message for when it cleans 0.00 bytes from a project. After running this at my `$HOME`:...
I (and many other people) configue cargo to use a single `target` dir shared between all projects, by putting something like this in `~/.cargo/config`: ```toml [build] target-dir = "/Users/iyes/.cargo/target" ```...
It would be useful to be able to use this tool's functionality from Rust code without having to go through the CLI. Is that something that could realistically be added?