templix
Reading other people's Zig code is usually a joy, as is writing it
Staying clear
That's my experience with bounties: someone does the job because they get paid, not because they have a particular interest in the issue, and then they instantly move on, leaving the submission to rot.
I agree with ZSF here.
Number of memory bugs in several fairly huge projects: 0
Zig is way more maintainable, leads to less code which translates to fewer bugs
How about that?
Zig is vastly safer than Rust unsafe. That's worth noting.
So while Rust's memory safety features is something I love, I absolutely hate the Rust community pushing mem safety as a panacea.
In my line of work, as an embedded programmer, Zig is vastly more appropriate.
Rust and Zig can co-exist just fine.
This was actually my impression after reading the post. A bad programmer making a lot of ill-informed complaints. Zig is an unfinished low-level language. Not suitable for bad programmers.
To define a subset of SVG doesn't imply that simplifying the XML part is going to be easy.
Yes, but SVG requires a lot of those optional bits... A parser complex enough to deal with all the nooks and corners of SVG is not simple at all.
If you take the expression above and format it in any half-decent editor, it's pretty clear. YAML is a shitshow, JSON is yuck and let's not talk about XML.
The sad truth is that many issues go unreported because people are lazy and move on when they hit a roadblock.
Also, I've seen this problem reported more than a few times so you're not alone.