This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/29266] Rule that binding rvalue to a refernce need a copy ctor don't work
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Oct 2006 20:33:33 -0000
- Subject: [Bug c++/29266] Rule that binding rvalue to a refernce need a copy ctor don't work
- References: <bug-29266-13316@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from pinskia at gcc dot gnu dot org 2006-10-01 20:33 -------
(In reply to comment #3)
> Plesae seee Comment #2 From Kelvin 2006-09-28 23:25 [reply].
>
> In addition 2 questions I raised in the Commet2. I also have one more question
> about the rule "bind an rvalue to a reference,
> we need to let copy ctor of the class be accessible.", I found that this rule
> only effective when the reference is delcared as "const &", but if we remove
> keyword "const", then "no matching" happen again.
Because it will not be a copy constructor that can bind a rvalue to a reference
at that point so this is still not a bug.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29266