public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58265] std::string move assignment should be noexcept
Date: Wed, 28 Aug 2013 21:57:00 -0000	[thread overview]
Message-ID: <bug-58265-4-p5FiTsGtft@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58265-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58265

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.9.0                       |---

--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> ---
As a matter of fact, isn't, in our current implementation, because std::swap
itself isn't in case the allocators are not equal.

I can preliminarily adjust it for ext/vstring.h (a preview of the future c++11
conforming basic_string) but it still needs work as regards the C++11 memory
allocation model.


  parent reply	other threads:[~2013-08-28 21:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 21:27 [Bug libstdc++/58265] New: " f.heckenbach@fh-soft.de
2013-08-28 21:48 ` [Bug libstdc++/58265] " paolo.carlini at oracle dot com
2013-08-28 21:57 ` paolo.carlini at oracle dot com [this message]
2013-08-31 10:21 ` daniel.kruegler at googlemail dot com
2013-09-20 15:50 ` [Bug libstdc++/58265] [lwg/2063] " glisse at gcc dot gnu.org
2013-09-24 10:07 ` glisse at gcc dot gnu.org
2015-07-17 11:14 ` redi at gcc dot gnu.org
2015-09-11 11:02 ` redi at gcc dot gnu.org
2015-09-11 11:03 ` 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-58265-4-p5FiTsGtft@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: link
Be 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).