[cwillu]

The thing I hate about rust is that compiling a small app immediately creates 100gb of junk, and that junk doesn't live in the responsible project's folder, and that junk doesn't get cleaned up by anything.

[pdimitar]

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]

I’m at 227GB as I write this.

[pdimitar]

Super 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]

PLEASE_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]

I 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.

[valcron1000]

Had no nuke the `target` folder a couple of weeks ago, +400 GB ...

[capitainenemo]

Many rust nightly versions + no clean / sweep / clean-all?

[kstrauser]

Just the one version, but lots of test builds in quick succession.

[cwillu]

“Linux System Requirements: 3.2MB [+ 17GB the first day]”