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

[Kagamin via Digitalmars-d]

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.