Congratulations and thank you to all who worked on this accomplishment! I see the self-hosted compiler as a dam with several years of potential pooled behind it. Now that the self-hosted compiler is enabled by default, I feel like the dam is about to burst and we will see a flood of changes coming much faster. Just looked through accepted language proposals and I’m excited :)
Fantastic work! Although I’m rather disappointed by the changes to make a _ = unused_var a compile-time error in the name of clarity (this is on top of making unused variables a fatal error in Zig 0.8), I’m excited to see the development of the stage2 compiler and look forward to the completion of async, when I’ll be able to migrate a few of my projects over. I’m especially licking my lips over the planned for (0..100) {} range syntax, which will make iterating over matrices and such much more ergonomic.
Which is why I’m curious when Zig 0.10.1 will be released. I’m assuming it’ll be at the end of the next 6-month period in April, give or take a few weeks; is this correct?
Although I’m rather disappointed by the changes to make a _ = unused_var a compile-time error in the name of clarity
This is apparently a controversial subject (as anyone who follows Zig development knows), but I feel the exact opposite: with this change, as a reader of Zig code, when I see _ = unused_var; I know that unused_varis actually unused, and I no longer need to mentally keep track of that variable as I read through the code.
Congratulations and thank you to all who worked on this accomplishment! I see the self-hosted compiler as a dam with several years of potential pooled behind it. Now that the self-hosted compiler is enabled by default, I feel like the dam is about to burst and we will see a flood of changes coming much faster. Just looked through accepted language proposals and I’m excited :)
Fantastic work! Although I’m rather disappointed by the changes to make a
_ = unused_vara compile-time error in the name of clarity (this is on top of making unused variables a fatal error in Zig 0.8), I’m excited to see the development of the stage2 compiler and look forward to the completion of async, when I’ll be able to migrate a few of my projects over. I’m especially licking my lips over the plannedfor (0..100) {}range syntax, which will make iterating over matrices and such much more ergonomic.Which is why I’m curious when Zig 0.10.1 will be released. I’m assuming it’ll be at the end of the next 6-month period in April, give or take a few weeks; is this correct?
This is apparently a controversial subject (as anyone who follows Zig development knows), but I feel the exact opposite: with this change, as a reader of Zig code, when I see
_ = unused_var;I know thatunused_varis actually unused, and I no longer need to mentally keep track of that variable as I read through the code.Generally bugfix releases such as 0.10.1 are released as soon as all the issues in the milestone are completed: https://github.com/ziglang/zig/milestone/18
Where can I find documentation about Zig multi-threading?
Did you look at the stdlib documentation, or are you looking for something else? Here is a short example from ziglearn.org.
If I’m not mistaken, apart from threads, zig also has some async features that should get a bit more love in the future™️.