public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/30578] array_allocator can't be safely copied Date: Thu, 01 Feb 2007 12:20:00 -0000 [thread overview] Message-ID: <20070201122001.23228.qmail@sourceware.org> (raw) In-Reply-To: <bug-30578-13986@http.gcc.gnu.org/bugzilla/> ------- 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
next prev parent reply other threads:[~2007-02-01 12:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-24 20:00 [Bug libstdc++/30578] New: " skottmckay at gmail dot com 2007-01-24 20:02 ` [Bug libstdc++/30578] " skottmckay at gmail dot com 2007-02-01 12:20 ` bkoz at gcc dot gnu dot org [this message] 2007-02-01 13:01 ` bkoz at gcc dot gnu dot org 2007-02-07 21:58 ` skottmckay at gmail dot com [not found] <bug-30578-4@http.gcc.gnu.org/bugzilla/> 2014-05-07 18:52 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070201122001.23228.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).