On 2012-13-05 20:10, Jonathan M Davis <[email protected]> wrote:
It would be a _huge_ design mistake for a systems language not to have
nullable pointers. Having non-nullable references or pointers in
addition to nullable ones might be useful, but not having nullable ones
at all would be crippling - especially for a systems language.
Indeed. However, given both types, I would argue that non-nullable by
default would go best with the D design guidelines - safe before unsafe,
to be specific.
Of course, given the current state of D, retroactively fitting
non-nullable references/pointers by default is impossible, unwanted,
and simply a bloody stupid idea.
--
Simen
