Re:I am not yet ready to switch to Zig from Rust
by ilrwbwrkhv on Friday June 14, 2024 @03:36PM
(#40684218)
> Could just do null -> none, nonnull -> some, optional doesn't introduce anything new here. Either you null check or you optional check
I am not sure what you mean by the first point but what I am saying is that the compiler doesn't stop you from having a basic runtime null pointer exception because of "simplicity" and "yagni".
Optionals are just another outlet for "best practice" bullshittery and not much else. If go doesn't have, sounds like they're following YAGNI principle