Thank you, so many great features. My personal favorite is .declLiteral() syntax, which makes webserver route-configuration very easy and readable!
If you are ever in temptation to do a builder for internal DSL, .declLiteral() might be a better way. I think it might be very cool for GUI structures too.
I did a quick PoC for SQL query building, but unfortunately, any more advanced queries are better to copy & serialize their arguments for safety reasons, so not that useful there, but still, very hyped about this particular thing.
There's something weird about the example that's being given. Coming from C it feels like I am making my struct much bigger... But is it implemented as a pointer to another struct ?
We're probably going to add support for cross-compiling FreeBSD's libc in the near future (and I imagine the other BSDs as well). From there, I think the only blocker for Tier 1 is getting it built and tested in CI.
My understanding is that Zig's incremental compilation will work on a much more granular level (i.e. functions, etc), so, for example, change one function and only that function (and its dependencies) will get recompiled/relinked (there's some linker trickery involved to avoid needing to relink everything IIUC).
Hm, I didn't think to add Haiku to the support table. It's probably Tier 3; the standard library support is minimal, and we don't support cross-compiling its libc. Patches definitely welcome.
If you are ever in temptation to do a builder for internal DSL, .declLiteral() might be a better way. I think it might be very cool for GUI structures too.
I did a quick PoC for SQL query building, but unfortunately, any more advanced queries are better to copy & serialize their arguments for safety reasons, so not that useful there, but still, very hyped about this particular thing.