From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13308 invoked by alias); 9 Aug 2010 13:39:17 -0000 Received: (qmail 13209 invoked by alias); 9 Aug 2010 13:38:49 -0000 Date: Mon, 09 Aug 2010 13:39:00 -0000 Message-ID: <20100809133849.13207.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/45228] [C++0x] Can't copy-construct "tuple" from "const tuple" rvalue In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jason at redhat dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-08/txt/msg00647.txt.bz2 ------- Comment #5 from jason at redhat dot com 2010-08-09 13:38 ------- Subject: Re: [C++0x] Can't copy-construct "tuple" from "const tuple" rvalue On 08/09/2010 09:31 AM, paolo dot carlini at oracle dot com wrote: > I'm also thinking that the weird constructor tuple(tuple<_UElements...>& __in), > which has been suggested at the time by Peter Dimov, falls under the same > reasoning and should be removed, the actual issue sorted out elsewhere again > through SFINAE. Removed? To be clear, I was suggesting that you keep the constructor, just prevent it from being selected when the deduced parameter type is reference-related to the enclosing class. Jason -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45228