Struct should be invalid after move

[Stanislav Blinov]

On Tuesday, 27 November 2018 at 12:14:17 UTC, Jonathan M Davis 
wrote:

> Well, if the compiler were doing the move...

[wall snipped]

> And simply flagging common functions that do moves isn't going 
> to be enough to catch all cases - especially when all it takes 
> to hide the fact that a move occurred is to wrap the move call 
> in another function that the compiler doesn't have visibility 
> into thanks to separate compilation.

"Easy" enough. The move and emplace families should be compiler 
intrinsics, not library functions.