Most 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.