This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [patch] No allocation for empty unordered containers
- From: Jonathan Wakely <jwakely at redhat dot com>
- To: François Dumont <frs dot dumont at gmail dot com>
- Cc: "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>
- Date: Tue, 5 Aug 2014 21:10:26 +0100
- Subject: Re: [patch] No allocation for empty unordered containers
- Authentication-results: sourceware.org; auth=none
- References: <538E339A dot 3010709 at gmail dot com> <53D2C3D4 dot 8060601 at gmail dot com> <20140804114914 dot GO2361 at redhat dot com> <20140804115539 dot GP2361 at redhat dot com> <53E13810 dot 8030107 at gmail dot com>
On 05/08/14 22:01 +0200, François Dumont wrote:
On 04/08/2014 13:55, Jonathan Wakely wrote:
If we don't make it noexcept then I see no point in avoiding
allocation.
(And if the functors and allocator can throw then the noexcept might
have to be condition.)
So please make sure we get that change as well during stage 1.
Hi
I know why move constructor must be noexcept but why default must
be too ?
It doesn't have to be noexcept, but IMHO there is no point changing
the containers to avoid allocation unless that allows us to mark it
noexcept. If it can throw anyway, we might as well allocate the
initial buckets.