You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Rust compiler, rustc, can generate a ton of artifacts in compilation, ranging from dependencies and macros to generated code and intermediate files. Users should be warned that if they choose to compile the program for source, they should keep an eye on the associated files and their impact on disk usage on the host.
For users looking to understand the impact, they can look at the target/ directory. Users relying on the executable should not have this problem.
The text was updated successfully, but these errors were encountered:
It's a really good idea, I think.
I actually faced that kinda disk full issue while I was working on my Windows VPS machine which has low capacity of hard disks.
At that time, I used cargo run command and multiple download of libraries seem to pile up my disk and it finally made my VPS to get stuck.
In my case cargo clean command worked fine for deleting the cache files which is large.
Plus, when we use bazel run, I think bazel clean --expunge command would work fine.
Of course, it's true that it's a simple general knowledge but we should target novice users as well, I think.
Thanks.
The Rust compiler,
rustc
, can generate a ton of artifacts in compilation, ranging from dependencies and macros to generated code and intermediate files. Users should be warned that if they choose to compile the program for source, they should keep an eye on the associated files and their impact on disk usage on the host.For users looking to understand the impact, they can look at the
target/
directory. Users relying on the executable should not have this problem.The text was updated successfully, but these errors were encountered: