On Saturday, 23 July 2016 at 13:18:03 UTC, Rufus Smith wrote:
Trying to compare a *ptr value with a value in nogc code
results in the error:
Error: @nogc function '...' cannot call non-@nogc function
'object.opEquals'
Shouldn't object opEquals be marked?
If object.opEquals is marked @nogc, than all D classes must
implement it as @nogc, because (of course) you cannot override a
@nogc method with a not-@nogc one (while the opposite is
possible, of course).
So marking it @nogc is not only a big breaking change, but also
very limiting.
