> 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

> 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".