On 15.06.2012 18:27, bearophile wrote:
Dmitry Olshansky:

If that is sole concern, I suggest do a pull that makes enforce vs
assert decision accessible from the outside:

NotNull!(T, NotNull.Strict) //asserts
NotNull!T //throws

Nullable isn't the only problem, there are similar problems with
std.random.uniform. How do you tell uniform() what kind of
Nullable to use?

why would uniform have to do anything with nullable?
If anything it's handled like always via tempaltes.


--
Dmitry Olshansky

Reply via email to