[v3 PATCH] Make any's copy assignment operator exception-safe, don't copy the underlying value when any is moved, make in_place constructors explicit.

Jonathan Wakely jwakely@redhat.com
Mon Oct 10 22:01:00 GMT 2016

On 10/10/16 22:21 +0300, Ville Voutilainen wrote:
>> This code was all pretty carefully written to avoid any redundant
>> operations. Does this change buy us anything except simpler code?
>As discussed, destroying the value but leaving the manager non-null will
>do bad things.

Oops again on my part! Not so carefully written, or tested.

>New patch attached, ok for trunk?

OK, thanks.

More information about the Libstdc++ mailing list