https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67773
--- Comment #6 from Adam Wenocur ---
Whoops! Sorry about the malformed double-post.
Another way of explaining the problem is that the compiler appears to be
suppressing the wrong destructor call. Since this is a move and not a copy, or
in C++03
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67773
--- Comment #5 from Adam Wenocur ---
(In reply to Jonathan Wakely from comment #3)
> Oh, are you expecting this:
>
> a_thing = demo(demo::second);
>
> to have the same behaviour as this:
>
> a_thing.~demo();
> new(&a_thing) demo(demo::se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67773
--- Comment #4 from Adam Wenocur ---
(In reply to Jonathan Wakely from comment #3)
> Oh, are you expecting this:
>
> a_thing = demo(demo::second);
>
> to have the same behaviour as this:
>
> a_thing.~demo();
> new(&a_thing) demo(demo::se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67773
--- Comment #1 from Adam Wenocur ---
compiler output:
-*- mode: compilation; default-directory: "~/compiler-test/" -*-
Compilation started at Wed Sep 30 00:45:55
./compile.sh
: 4.8.4
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: awenocur at aol dot com
Target Milestone: ---
Created attachment 36420
--> https://gcc.gnu.org/bugzi
