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++/52433] [C++11] debug mode iterators need to move Date: Wed, 29 Feb 2012 13:02:00 -0000 [thread overview] Message-ID: <bug-52433-4-EBK2BSYi1p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52433-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52433 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-29 13:01:25 UTC --- Also untested, and sub-optimal (swapping would be better than copying): /** * @brief Move assignment. * @post @p __x is singular and unattached */ _Safe_iterator& operator=(_Safe_iterator&& __x) { _Safe_iterator __tmp(std::move(__x)); *this = __tmp; return *this; }
next prev parent reply other threads:[~2012-02-29 13:01 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-29 12:53 [Bug libstdc++/52433] New: [C++11] debug mode iterators need move constructors redi at gcc dot gnu.org 2012-02-29 12:58 ` [Bug libstdc++/52433] [C++11] debug mode iterators need to move redi at gcc dot gnu.org 2012-02-29 13:02 ` redi at gcc dot gnu.org [this message] 2012-02-29 14:39 ` redi at gcc dot gnu.org 2012-02-29 15:37 ` paolo.carlini at oracle dot com 2012-02-29 16:45 ` redi at gcc dot gnu.org 2012-02-29 17:19 ` paolo.carlini at oracle dot com 2012-03-01 6:49 ` daniel.kruegler at googlemail dot com 2012-03-01 9:35 ` redi at gcc dot gnu.org 2012-03-04 12:50 ` redi at gcc dot gnu.org 2012-03-04 13:00 ` redi at gcc dot gnu.org 2012-03-08 1:05 ` redi at gcc dot gnu.org 2012-03-08 22:31 ` redi at gcc dot gnu.org 2012-03-23 0:05 ` redi at gcc dot gnu.org 2012-03-23 0:35 ` 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-52433-4-EBK2BSYi1p@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).