[patch] libstdc++/61143 make unordered containers usable after move
Paolo Carlini
paolo.carlini@oracle.com
Thu May 15 20:31:00 GMT 2014
Hi,
On 05/15/2014 10:20 PM, François Dumont wrote:
> Hi
>
> Here is a proposal to fix PR 61143. As explained in the PR I
> finally prefer to leave the container in a valid state that is to say
> with a non zero number of bucket, that is to say 1, after a move. This
> bucket is stored directly in the container so not allocated to leave
> the move operations noexcept qualified. With this evolution we could
> even make the default constructor noexcept but I don't think it has
> any interest.
Well, FWIW my opinion (I didn't follow the issue in detail), I think it
would be a very nice improvement, not only because of the noexcept, but
because of the avoided dynamic memory allocation, thus performance. I'm
sure many other implementors agree ;)
Paolo.
More information about the Libstdc++
mailing list