This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/64865] std::allocator::construct/destroy not called for specialization of std::allocator<trivialtype>
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 30 Jan 2015 09:51:37 +0000
- Subject: [Bug libstdc++/64865] std::allocator::construct/destroy not called for specialization of std::allocator<trivialtype>
- Auto-submitted: auto-generated
- References: <bug-64865-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64865
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Casey Carter from comment #0)
> * Close this bug report as WONTFIX since it is horrible design to specialize
> std::allocator instead of declaring a new allocator type; given that
> container implementations are free to rebind to a different specialization,
> there is no guarantee that functionality added to a user-defined
> specialization will even be used.
This.