public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "f.heckenbach@fh-soft.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/58265] New: std::string move assignment should be noexcept Date: Wed, 28 Aug 2013 21:27:00 -0000 [thread overview] Message-ID: <bug-58265-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58265 Bug ID: 58265 Summary: std::string move assignment should be noexcept Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: f.heckenbach@fh-soft.de According to http://www.cplusplus.com/reference/string/string/operator=/, the std::string move assignment operator should be noexcept. #include <string> static_assert (std::is_nothrow_move_assignable <std::string>::value, "failed");
next reply other threads:[~2013-08-28 21:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-28 21:27 f.heckenbach@fh-soft.de [this message] 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 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@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).