←back to thread

Zig breaking change – Initial Writergate

(github.com)
228 points Retro_Dev | 5 comments | 04 Jul 25 04:11 UTC | HN request time: 0.368s | source
Show context
barelysapient ◴[04 Jul 25 15:03 UTC] No.44465168[source]▶
A big change like this makes me hopeful Zig may revisit and improve other design choices in the future.
replies(1): >>44466074 #
bbkane ◴[04 Jul 25 16:54 UTC] No.44466074[source]▶
Could you elaborate on the choices you'd like revisited?
replies(3): >>44466265 #>>44470288 #>>44472856 #
1. 90s_dev ◴[04 Jul 25 17:16 UTC] No.44466265[source]▶
Unused variables stops all further compilation, so that even future errors can't be seen until the variable is used.
replies(2): >>44467902 #>>44468527 #
2. Mond_ ◴[04 Jul 25 21:08 UTC] No.44467902[source]▶
Meh.

I think this should be a warning on debug builds and an error on release builds, but it's a relatively minor thing and not a deal breaker by any means.

If this is the worst thing that people would like to see revisited, Zig must be doing amazingly well.

replies(1): >>44469251 #
3. mlugg ◴[04 Jul 25 22:41 UTC] No.44468527[source]▶
This is simply not true. See https://zigbin.io/f57b94/run.

(That link seems to show the "unused local variable" error line twice for me; that's some kind of bug with this zigbin service and does not reproduce when running the Zig compiler normally.)

4. josephg ◴[05 Jul 25 00:52 UTC] No.44469251[source]▶
> but it's a relatively minor thing and not a deal breaker by any means.

It totally breaks my normal workflow. I don’t use zig at all because of this misfeature. Warn in debug and error on release builds would be strange but fine.

replies(1): >>44471738 #
5. ◴[05 Jul 25 10:41 UTC] No.44471738{3}[source]▶