https://issues.dlang.org/show_bug.cgi?id=17897

--- Comment #9 from Jack Applegame <japplegame@gmail.com> ---
Seems this bug related to https://issues.dlang.org/show_bug.cgi?id=17246

--

https://issues.dlang.org/show_bug.cgi?id=17897

Temtaime <temtaime@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |temtaime@gmail.com

--- Comment #10 from Temtaime <temtaime@gmail.com> ---
After fixing https://issues.dlang.org/show_bug.cgi?id=17246 this outputs:

Bar.this(int): 14FB84
fun: 14FB20
Bar.~this(): 14FB20

Object gets moved without notification.
This should not behave this way

--

https://issues.dlang.org/show_bug.cgi?id=17897

--- Comment #11 from Steven Schveighoffer <schveiguy@yahoo.com> ---
(In reply to Temtaime from comment #10)
> After fixing https://issues.dlang.org/show_bug.cgi?id=17246 this outputs:
> 
> Bar.this(int): 14FB84
> fun: 14FB20
> Bar.~this(): 14FB20
> 
> Object gets moved without notification.
> This should not behave this way

This is perfectly valid. You are allowed to move a struct without calling the postblit. See the spec here: https://dlang.org/spec/struct.html

"A struct is defined to not have an identity; that is, the implementation is free to make bit copies of the struct as convenient."

In fact, I think we can close this as a duplicate, as it now works properly.

However, I'm kind of surprised there is a move here, should be unnecessary if implemented properly.

--

https://issues.dlang.org/show_bug.cgi?id=17897

Steven Schveighoffer <schveiguy@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #12 from Steven Schveighoffer <schveiguy@yahoo.com> ---
Closing as duplicate

*** This issue has been marked as a duplicate of issue 17246 ***

--