3 ms·

One of the features in go that makes it workable is you can assign it away via: _ = somevar That eliminates the unused chain problem. Not sure if zig included

One of the features in go that makes it workable is you can assign it away via: _ = somevar That eliminates the unused chain problem. Not sure if zig included that part of the feature as well. Generally I agree though. The main problem with forcing unused variables, imo, is that it forces you to think a certain way. When I'm exploring the solution space on something, those constraints feel inhibiting.

alpaca128 4y ago
> you can assign it away via: _ = somevar If one suggested this in any other language to suppress "unused variable" warnings it would be considered a lazy way to avoid fixing the issue. Meanwhile the developer of Zig himself recommended doing this[0] which only shows what a bad idea it is to make this a compiler error imho. It encourages workarounds and enforces something we automated long ago in the form of dead code elimination. [0] https://github.com/ziglang/zig/issues/335#issuecomment-435267965 https://github.com/ziglang/zig/issues/335#issuecomment-43526...
- hactually 4y ago
  It's how Go works...