Zig 0.16.0 Release Notes
ziglang.org
Zig 0.16.0 Release Notes
1–10 of 44 posts
Re: Zig 0.16.0 Release Notes
#2The "Juicy Main" looks like a very nice QoL feature. Gets rid of all the boilerplate for allocators and argv.
Re: Zig 0.16.0 Release Notes
#3The "Juicy Main" looks like a very nice QoL feature. Gets rid of all the boilerplate for allocators and argv.
It's the dark horse of this release as CLI parsing can also be more easily built on top of it. There's a couple of proposals floating around now, so I hope we get something soon-ish (maybe in 0.18 since a short cyle is planned for 0.17).
Re: Zig 0.16.0 Release Notes
#4I've been waiting eagerly for this release ever since the new Io interface was announced. Pumped to start working on some new projects with this!
Love this line from the release notes:
> Lo! Lest one learn a lone release lesson, let proclaim: "cancelation" should seriously only be spelt thusly (single "l"). Let not evil, godless liars lead afoul.
Re: Zig 0.16.0 Release Notes
#5What a banger of a release. The new `Io` interface was a huge breaking change for my project, but I made the transition. Zig seems to be pulling the same trick it pulled with allocators: just make it an explicit value that you pass around. Explicit allocators felt obviously right in retrospect, and so far this feels obviously right too.
Re: Zig 0.16.0 Release Notes
#6Obviously, I/O as an interface is the headliner here, but there are lots of other goodies to pay attention to, such as the "juicy main".
Small integers auto coercing into floats is a nice gift to game devs. It's nice that game dev is acknowledged as one of the niches Zig can target as I believe it could really thrive there due to how easily it can integrate with C & C++. Or, rather, more easily than the alternatives.
Re: Zig 0.16.0 Release Notes
#7What a banger of a release. The new `Io` interface was a huge breaking change for my project, but I made the transition. Zig seems to be pulling the same trick it pulled with allocators: just make it an explicit value that you pass around. Explicit allocators felt obviously right in retrospect, and so far this feels obviously right too.
The approach feels like a natural extension of Zig's philosophy about explicitness around low-level operations (no hidden control flow, no hidden memory allocations, etc.). Your function can be blocking? Communicate that through the function signature! Very in style for the language.
Re: Zig 0.16.0 Release Notes
#8The "Juicy Main" looks like a very nice QoL feature. Gets rid of all the boilerplate for allocators and argv.
It's the dark horse of this release as CLI parsing can also be more easily built on top of it. There's a couple of proposals floating around now, so I hope we get something soon-ish (maybe in 0.18 since a short cyle is planned for 0.17).
This sounds interesting to me - could you elaborate a little on what things are in those proposals?
Re: Zig 0.16.0 Release Notes
#9Earlier quoted context omitted.
It's the dark horse of this release as CLI parsing can also be more easily built on top of it. There's a couple of proposals floating around now, so I hope we get something soon-ish (maybe in 0.18 since a short cyle is planned for 0.17).
This sounds interesting to me - could you elaborate a little on what things are in those proposals?
Sure, this is the issue tracking the work: https://codeberg.org/ziglang/zig/issues/30677
The idea is to offer some kind of CLI parsing in the std. It says minimal, but the discussion also veers into some more advanced options.
The discussion resulted in two PRs (that I know of):
- Type-driven: https://codeberg.org/ziglang/zig/issues/30677
@dotcarmen extracted it into a package (https://codeberg.org/dotcarmen/clip) so people could more easily try it out.
- Composition-based: https://codeberg.org/ziglang/zig/pulls/31620
If you're familiar with Rust's clap, it's a bit like derive vs builder API.
You can also see how each approach would look in practice if you inspect the diff for the "tools" directory on the PRs.
Re: Zig 0.16.0 Release Notes
#10The "Juicy Main" looks like a very nice QoL feature. Gets rid of all the boilerplate for allocators and argv.
Do I get it right that this is everything you need for a typical CLI tool?