Status of std::deque improvements

[François Dumont]

Note that on my side I had also work on it. At the beginning it was more 
an attempt to default constructors like I did for other containers but 
eventually I had to do a little like you did.

Here is the patch, I'll have a look to yours to see differences and 
surely pick up some good ideas from yours.

François


On 20/08/2018 13:11, Jonathan Wakely wrote:
> On 18/08/18 19:16 +0100, Stephan Dollberg wrote:
>> Hello,
>>
>> I am wondering what the status of the planned std::deque improvements 
>> is (making move operations non-throwing and the issues 24693 and 77524)?
>>
>> I see that there was a patch in discussion 
>> (https://gcc.gnu.org/ml/libstdc++/2016-10/msg00017.html) and also 
>> talks of merging that for gcc 8 
>> (https://gcc.gnu.org/ml/gcc-help/2017-08/msg00104.html) but that 
>> didn't seem to have happened.
>
> The changes didn't work. There was a bug caused by one of them which I
> didn't manage to diagnose and fix.
>
> I'll try to get it working some time, but it's not a priority because
> it can only be changed for the ABI-breaking
> --enable-symvers=gnu-versioned-namespace mode, which is only used by a
> tiny fraction of our users.
>
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: deque_defaulted_move.patch
Type: text/x-patch
Size: 31450 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20180820/997dffad/attachment.bin>