On Wednesday, 29 May 2013 at 13:36:16 UTC, Regan Heath wrote:
Which default behaviour? D's references/pointers? Or the
proposed NotNull!(T) library solution?
The default behavior. The one you get our of the box. So not
NonNullable.
This behavior isn't useful. You'll find no argument except
historical reason (which is a very valid argument BTW) to keep
that. Everything else is backward rationalization.
If @disable is insufficient for a NotNull!(T) which does what
we need it to do, then more features are required. Ignoring
the bugs in @disable, do you believe it is insufficient? If
so, can you give us some example usages it does not yet
support/allow/provide for.
I don't know what you answer to, but clearly not what you are
quoting.
