4 ms·
Could just do null -> none, nonnull -> some, optional doesn't introduce anything new here. Either you null check or you optional check Optionals are just anoth
by matrix87 2y ago
Could just do null -> none, nonnull -> some, optional doesn't introduce anything new here. Either you null check or you optional check
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
- ilrwbwrkhv 2y ago> 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".