public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jwakely dot gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/40486] [c++0x] rvalue-references no longer bind to lvalues Date: Tue, 23 Jun 2009 18:40:00 -0000 [thread overview] Message-ID: <20090623184014.28154.qmail@sourceware.org> (raw) In-Reply-To: <bug-40486-15652@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from jwakely dot gcc at gmail dot com 2009-06-23 18:40 ------- The library pieces of Doug's patch that still need to be applied are: * include/std/tuple (_Tuple_impl): Use lvalue references when explicitly specifying the template argument to std::move. * include/std/iosfwd (operator<<): Provide a forwarding operator<< that accepts rvalue streams. (operator>>): Ditto. * include/bits/stl_iterator.h (move_iterator::operator*): Explicitly std::move the result, to convert it to an rvalue reference. * include/bits/stl_move.h (forward): Forward lvalues (which may end up being turned into rvalues). (move): Explicitly static_cast to an rvalue. * testsuite/27_io/rvalue_streams.cc: New; test the use of rvalue streams. Works except for the fact that we can't call str() on the result. (This is an existing issue). I think the move_iterator and tuple changes would be OK to apply now but the stream parts have a FIXME and as discussed, the definition of std::move is undecided. I'll come back to this soon. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40486
next prev parent reply other threads:[~2009-06-23 18:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-18 11:52 [Bug c++/40486] New: " dragan at plusplus dot co dot yu 2009-06-18 11:57 ` [Bug c++/40486] " paolo dot carlini at oracle dot com 2009-06-18 13:11 ` jwakely dot gcc at gmail dot com 2009-06-18 13:14 ` jwakely dot gcc at gmail dot com 2009-06-18 14:19 ` dragan at plusplus dot co dot yu 2009-06-18 15:40 ` jwakely dot gcc at gmail dot com 2009-06-18 16:26 ` jason at redhat dot com 2009-06-18 17:09 ` dragan at plusplus dot co dot yu 2009-06-19 12:05 ` dragan at plusplus dot co dot yu 2009-06-23 18:40 ` jwakely dot gcc at gmail dot com [this message] 2009-06-30 12:11 ` jwakely dot gcc at gmail dot com 2009-08-01 9:44 ` paolo dot carlini at oracle dot com
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=20090623184014.28154.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).