This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [RFC] Removal of allocator::construct / destroy vs our containers
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: Paolo Carlini <pcarlini at suse dot de>
- Cc: Matt Austern <austern at google dot com>, libstdc++ <libstdc++ at gcc dot gnu dot org>
- Date: Thu, 03 May 2007 14:25:01 +0200
- Subject: Re: [RFC] Removal of allocator::construct / destroy vs our containers
- References: <463127A8.9050804@suse.de> <4631DA16.8020604@redhat.com> <4631DD0C.1060706@suse.de> <4632B1BE.5020604@suse.de> <46370A29.3070100@redhat.com> <e3a529600705011028k4feffbcbtfa495fb63e1c202a@mail.gmail.com> <463779E1.9020905@suse.de> <46377F4B.7090405@suse.de> <4637BF65.4090607@suse.de>
PS: IMO, in case we end keeping those allocator members and, as a
consequence, we keep on calling them from the containers, we have to
improve the dispatchings in stl_construct.h and stl_uninitialized.h to
avoid allocators by value. Seems doable, after all, only more complex...
Agreed, this would be nice.
For concreteness, the below appear to work, regetests fine
(unfortunately some tweaks to rope are needed, but otherwise the
infrastructure in place seems already ok...)
Cool! I guess this waits for a more elaborate discussion in Toronto as
well...
-benjamin