From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31788 invoked by alias); 18 Apr 2011 11:48:13 -0000 Received: (qmail 31778 invoked by uid 22791); 18 Apr 2011 11:48:12 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 Apr 2011 11:47:17 +0000 From: "daniel.kruegler at googlemail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/48531] [C++0x][SFINAE] Hard errors with arrays of unknown bound X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: daniel.kruegler at googlemail dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.7.0 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Date: Mon, 18 Apr 2011 11:48:00 -0000 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: 2011-04/txt/msg01856.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D48531 --- Comment #11 from Daniel Kr=C3=BCgler 2011-04-18 11:47:15 UTC --- (In reply to comment #10) > It is not accepted. >=20 > I tried again to remove the special code for is_default_constructible in > and a number of static_asserts, all having to do with arrays > fired... I was wrong, I just notice that the FDIS wording says in regard to the expression T() in [expr.type.conv] p. 2: "The expression T(), where T is a simple-type-specifier or typename-specifi= er for a non-array complete object type or the (possibly cv-qualified) void ty= pe, creates a prvalue of the specified type,which is value-initialized" So, it seems that the current protection code in the library is necessary a= s of this wording, but I'm no longer sure that the core wording reflects the intention, because array rvalues are clearly supported.