cargo-sweep
cargo-sweep copied to clipboard
holmgr
A cargo subcommand for cleaning up unused build files generated by Cargo
Hello @holmgr, I noticed that there haven't been any PRs merged in the past year or so, even though there are a few useful and small PRs open. Are you...
Previously, cargo sweep would unconditionally give an error when it couldn't determine the fingerprint. But for custom toolchains, it makes sense for it to be linked but give an error...
I have a git with the following layout ``` . ├── Cargo.toml ├── app-wasm │ ├── Cargo.toml ├── cli │ ├── Cargo.toml ├── crates │ ├── api │ │ ├──...
I installed a custom version of rust from source (with x.py) and then cleaned the target directory. Now `cargo sweep -i` doesn't work. Instead of giving a hard error, it...
Since most likely this tool will get used in CI, it's really optimal to include built binaries in the releases. and advise users to download binaries in the following way...
Right now errors seem not to be printed correctly, and cargo-sweep exits with code 0 even on error. ```text $ cargo sweep --toolchains nightly-2019-13-13 # toolchain that does not exist...
https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#mtime-on-use What I mean is, in the README you should mention that this flags needs to be set. It takes a while to debug why it doesn't work, until finally...
I find the default output listing every file to delete, too noisy. So I wonder if it would be acceptable to make the default output quieter? If not I can...
How about making dry-run the default mode and instead having a `--delete` option say to enable actual deletion? That might be a friendlier approach: generally I like to see the...