On 5/29/13 5:20 AM, deadalnix wrote:
On Wednesday, 29 May 2013 at 07:50:39 UTC, Kenji Hara wrote:
Currently I recognize that it is necessary to fix compiler bugs around
@disable this(); at least.
@deadalnix, it seems to me that you argue that @disable this(); is
insufficient or useless to implement NotNull!T. If so, what is
necessary to
do it? What is impossible thing by NotNullT?
No I'm nto saying that this is impossible, I'm saying that @disable
this() and non nullable pointer are the exact same feature.
Implication is not equivalence.
Andrei
