DIP 1014:Hooking D's struct move semantics--Community Review Round 1

Kagamin spam at here.lot
Thu May 17 13:42:23 UTC 2018


Looks like requirement for @nogc @safe has no consequence as the 
DIP suggests to infer them anyway. On ideological side safety 
can't be a requirement because it would contradict its purpose of 
providing guarantee. Especially if the suggested use case is 
handling of dangling pointers.


More information about the Digitalmars-d mailing list