News for hackers. Stuff that matters.

A comment on Zig – io_uring and Grand Central Dispatch std.Io implementations landed. Parent comment

Re:Zig – io_uring and Grand Central Dispatch std.Io implemen... by jsheard on Saturday February 14, 2026 @07:04AM (#47013898)
> if you're a casual user (ie you don't follow the development) don't try incomplete APIs that not even the creators of fully know how they are supposed to work

Is the completeness of each API formally documented anywhere? Maybe I missed something but it doesn't seem like it is, in which case the only way to know would be to follow what's happening behind the scenes.

[ Parent | on HN ]
Re:Zig – io_uring and Grand Central Dispatch std.Io implemen... by Zambyte on Saturday February 14, 2026 @03:06PM (#47017874)
Zig cuts releases. This API is not on a release of Zig yet. It's only available through nightly builds of master. "Casual users" should stick to releases if they don't want to deal with incomplete APIs.
[ Parent | on HN ]
Re:Zig – io_uring and Grand Central Dispatch std.Io implemen... by the_mitsuhiko on Saturday February 14, 2026 @05:13PM (#47018929)
That's not really the issue. The stable API is incompatible with the API that will launch with 0.16. It's not really relevant if I'm playing with incompletely API, I want to know how I can migrate to it. I did not move yet to 0.16, but I wanted to see.

The migration pain will be the same once it launches unless they revert back, which does not seem likely at all.

But the point is: potentially every API is unstable.

[ Parent | on HN ]