4 ms·
FYI the Zig compiler that people are still using today is the C++ one. The self-hosted compiler hasn't been released yet. There's some Zig code running today in
by kristoff_it 4y ago
FYI the Zig compiler that people are still using today is the C++ one. The self-hosted compiler hasn't been released yet. There's some Zig code running today in the C++ compiler, but hasn't been there for the full life of the project and isn't the main source of bugs by far.
To this day I think the top 3 popular Zig projects are Bun, as you mentioned, then River [1] and TigerBeetle [2].
[1] https://github.com/riverwm/river https://github.com/riverwm/river
[2] https://github.com/tigerbeetledb/tigerbeetle https://github.com/tigerbeetledb/tigerbeetle
Up to you to decide how fine is the situation in those projects.
- littlestymaar 4y agoMost of the recent segfaults that have been fixed in Zig where Zig related, not caused by C++. (Without even mentioning the segfault in the std lib). And about tigerbeetle, this gives you an idea of how compelling the zig memory safety story is today: > All memory must be statically allocated at startup. No memory may be dynamically allocated (or freed and reallocated) after initialization. And then both river and bun have their shares of segfaults, with river looking substantially better than bun, but it suspect it also has much less usage in the wild. Overall, it looks pretty much like C as I said.