logoalt Hacker News

llm_nerd • today at 2:49 PM • 6 replies • view on HN

I wrote recently about a weird issue I encountered with Zig, though to be fair it was related to using Zig to compile C code, humorously in a Rust project (which touches on all of the languages mentioned in this post).

https://dennisforbes.ca/blog/microblog/2026/10/the_accidenta...

While I did just dismiss it as an edge issue, it turns out that this same rather clumsy sort of mistake has happened repeatedly in Zig's pure rewrite of MUSL. And despite being an absolutely catastrophically bad problem, by my judgment, the problem is still in main at this moment, across a wide number of musl function rewrites.

Which gives me pause about the whole zig project. If you're rewriting a critical library, making such simple but consequential mistakes shouldn't happen, and if they do happen it should be a red alert type situation.


Replies

senderista • today at 5:11 PM

Zig can be a hobby/learning project (in which case these elementary mistakes, and the lax development process that allowed them, are totally acceptable), or it can be a project that targets critical applications (like TigerBeetle, which handles REAL MONEY), but it can't be both.

lukaslalinsky • today at 3:59 PM

When working with Zig, you are a beta tester. The development process is unfortunately not great, so bugs slip in fairly easily. You need to be ready for it and test your application properly. Large Zig projects don't target the latest version. That said, if you can deal with that, you get a great language that is fun to use and very practical. I think it's worth it, even if it can be frustrating at times.

➕ show 1 reply
stateoff • today at 3:14 PM

Why not adding the link to the issue in the blog post?

https://codeberg.org/ziglang/zig/issues/37402

Looks like it is being worked on.

Personally I think it's not that catastrophic for zig < 1.0. Just a performance regression, and one can always link to other libc implementations, or is their own implementation enforced now?

➕ show 1 reply
drdexebtjl • today at 3:31 PM

strchr has no time complexity guarantees, by the way. This behavior is strictly correct.

➕ show 1 reply
dnautics • today at 3:03 PM

> Which gives me pause about the whole zig project

The whole zig project is like six people in a trenchcoat. You can't expect them to prioritize your one thing after 3 weeks

Did you make a PR?

➕ show 3 replies
chandlore • today at 4:25 PM

Andrew Kelley had a comment re this bug over at lobste.rs:

> I made the judgement call to let this slide in the review. I'm still not sure whether it was the right or wrong call.

https://lobste.rs/s/lh1j0e/shlemiel_painter_is_back_how_zig_...