Ziglang – robust, optimal, and maintainable programming language
github.com
github.com
How does Zig manages its memory ? I couldn't find any info on a garbage collector, so I assume the memory isn't dynamically-managed.
If it's statically managed, how is it done ? I it using some kind of region-based checking, like Rust with its borrow-checker ? Or is it 100% in the hands of the programmer ? (In which case, the «safety» argument is a bit strange).
https://news.ycombinator.com/item?id=19811183
https://news.ycombinator.com/item?id=19610199
https://hn.algolia.com/?query=Zig%20points%3E30&sort=byDate&...
EDIT: By markets I meant application categories, e.g. OS kernel, firmware, embedded, etc.
I'd already gathered that its closest competitors are C and Rust.
The single-page documentation is here: https://ziglang.org/documentation/master/
It seems like it would be attractive if you want a systems language that's much more modern than C (and comes with build and testing systems) but you're not interested in Rust's borrow-checker.
(C++ and other language programmers often conflate C with C++, but the two are really different languages.)