This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/30578] array_allocator can't be safely copied
- From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Feb 2007 12:20:01 -0000
- Subject: [Bug libstdc++/30578] array_allocator can't be safely copied
- References: <bug-30578-13986@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from bkoz at gcc dot gnu dot org 2007-02-01 12:20 -------
Should array_allocator be copy-constructable? I am not sure that the extra
effort to make _M_used shared in a mt-safe manner is worth it, for something
that is supposed to be write-once memory.
This is a deviation from the normal allocator interface, though.
Interesting.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30578