On: Compile-Time Evaluation in the Zig System Programming Language

I wondered about memory management too considering this language is supposed to "prioritize safety". Memory is manually managed though, which you can see from their HashMap example on the website.

The description indeed leaves a lot open to interpretation. They should have a brief overview that uses some standard terminology to describe Zig.

That's when using a custom allocator though, browsing through the other examples it doesn't look like there's any manual memory management going on but that could just be the examples chosen.

But it does an explicit free operation, and no mention of preventing double-frees, which to me implies it's unsafe.