Our Zig codebase had one leak and one undefined memory access. That was really surprising to me (in a good way). Our Zig codebase is large, complex, and uses tons of memory tricks for performance that could easily lead to unsafe behaviors. I thought we’d have a lot more issues, honestly. Also, the one leak found was during calling a 3rd party C API (so Zig couldn’t detect it). So this is a huge success.
– Mitchell Hashimoto
15 Likes
I enjoy reading all blog posts from Mitchell. They are always very insightful and informative. This one is no exception.
EDIT: Hacker News discussion We rewrote the Ghostty GTK application | Hacker News
2 Likes