Is it time for D 3.0?

[Adam D. Ruppe]

On Monday, 30 March 2020 at 21:24:31 UTC, rikki cattermole wrote:
> But in this case receive can be @nogc if the internals allow it 
> to be.

it can, this should be a trivial change.

> The only issue surrounding this is if somebody has decided to 
> inherit from one of the socket classes. Which is kinda a bad 
> thing to do regardless...

It is a useful thing to do - I did for SSL support, for example. 
But my ssl socket child class is also nogc compliant, as I 
suspect most people's would be.