Hacker News new | past | comments | ask | show | jobs | submit
quag | on: Zig – Type Resolution Redesign and Language Changes
That .zig-cache seems massive to me. I keep mine on a tmpfs and remove it every time the tmpfs is full.

Do you see any major problems when you remove your .zig-cache and start over?

latch | parent
Just a slower build. From ~20 seconds to ~65 seconds the first time after I nuke it.
h4ch1 | root | parent | next
But why is it so big in the first place?

I was searching around for causes and came across the following issues: https://github.com/ziglang/zig/issues/15358 which was moved to https://codeberg.org/ziglang/zig/issues/30193

The following quotes stand out

> zig's caching system is designed explicitly so that garbage collection could happen in one process simultaneously while the cache is being used by another process.

> I just ran WizTree to find out why my disk was full, and the zig cache for one project alone was like 140 GB.

> not only the .zig-cache directory in my projects, but the global zig cache directory which is caching various dependencies: I'm finding each week I have to clear both caches to prevent run-away disk space

Like what's going on? This doesn't seem normal at all. I also read somewhere that zig stores every version of your binary as well? Can you shed some light on why it works like this in zigland?

loading story #47331984
sgt | root | parent
Does Zig have incremental builds yet? Or is it 20 secs each time for your build.
loading story #47332001