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

[Kagamin]

On Thursday, 17 May 2018 at 13:50:26 UTC, Shachar Shemesh wrote:
> There is no such use case. Please remember that at the time 
> opPostMove is called, both new and old memory are still 
> allocated.

That's an interesting moment too. A struct that was supposed to 
be moved is copied instead and exists in two places 
simultaneously. Can't tell it yet, but it can have a hole in type 
system and opPostMove can only be trusted, not safe.