4 ms·
You're exaggerating quite a lot. Biggest I've seen the cargo directory after 3 months of active Rust development was ~17GB. You can also limit it with an env v
by pdimitar 3mo ago
You're exaggerating quite a lot. Biggest I've seen the cargo directory after 3 months of active Rust development was ~17GB.
You can also limit it with an env var. I have capped mine at 10GB.
- kstrauser 3mo agoI’m at 227GB as I write this.
- valcron1000 3mo agoHad no nuke the `target` folder a couple of weeks ago, +400 GB ...
- capitainenemo 3mo agoMany rust nightly versions + no clean / sweep / clean-all?
- pdimitar 3mo agoSuper curious then, and I stand corrected. You can put the `cargo clean gc` command on a daily/weekly schedule then, or configure the `gc` option in your Cargo config. Or set `CARGO_UNSTABLE_GC=true` in your shell init. Or all of the above.
- cwillu 3mo agoPLEASE_UNBREAK_ME options should default to on; people who actually work on rust code are quite capable of turning it off when they configure the rest of their environment.
- pdimitar 3mo agoI don't disagree. I can only assume it's defaulted to off due to many people working on big codebases and there constantly evicting cache would objectively slow them down. But, far from ideal for everyone else.