public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dragan at plusplus dot co dot yu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/40486]  New: [c++0x] rvalue-references no longer bind to lvalues
Date: Thu, 18 Jun 2009 11:52:00 -0000	[thread overview]
Message-ID: <bug-40486-15652@http.gcc.gnu.org/bugzilla/> (raw)

I'm surprised this hasn't been implemented already. AFAIK, it was
accepted and is in the current draft.

http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00436.html
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2844.html

The patch still applies to the compiler itself. However, the patch
doesn't handle issues addressed in update from N2831. Also, library
part doesn't apply, although I believe it would be trivial to update.


-- 
           Summary: [c++0x] rvalue-references no longer bind to lvalues
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: trivial
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dragan at plusplus dot co dot yu
 GCC build triplet: x86_64-linux-gnu
  GCC host triplet: x86_64-linux-gnu
GCC target triplet: x86_64-linux-gnu


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


             reply	other threads:[~2009-06-18 11:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 11:52 dragan at plusplus dot co dot yu [this message]
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
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=bug-40486-15652@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).