public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109305] Allocator copy in basic_string::operator= Date: Tue, 28 Mar 2023 16:19:43 +0000 [thread overview] Message-ID: <bug-109305-4-7XKKhavqcE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109305-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109305 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|WAITING |RESOLVED --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- Removing it would make the code less efficient and more complex. If your allocator is expensive to copy, your allocator is bad and should be fixed. They need to be cheap to copy.
next prev parent reply other threads:[~2023-03-28 16:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-27 19:04 [Bug libstdc++/109305] New: " marc-andre.laverdiere at synopsys dot com 2023-03-27 19:09 ` [Bug libstdc++/109305] " pinskia at gcc dot gnu.org 2023-03-27 19:12 ` pinskia at gcc dot gnu.org 2023-03-27 21:03 ` redi at gcc dot gnu.org 2023-03-28 16:04 ` marc-andre.laverdiere at synopsys dot com 2023-03-28 16:19 ` redi at gcc dot gnu.org [this message] 2023-03-28 16:21 ` redi at gcc dot gnu.org 2023-03-28 16:25 ` chgros at synopsys dot com 2023-03-28 16:35 ` redi at gcc dot gnu.org 2023-03-28 16:38 ` 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=bug-109305-4-7XKKhavqcE@http.gcc.gnu.org/bugzilla/ \ --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).