From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25974 invoked by alias); 17 May 2011 15:33:17 -0000 Received: (qmail 25965 invoked by uid 22791); 17 May 2011 15:33:16 -0000 X-SWARE-Spam-Status: No, hits=-2.7 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; Tue, 17 May 2011 15:33:03 +0000 From: "gdr at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/49022] [C++0x] std::begin and std::end specialized for std::valarray with some operators are missing. X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gdr at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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" MIME-Version: 1.0 Date: Tue, 17 May 2011 15:40: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-05/txt/msg01357.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49022 --- Comment #7 from Gabriel Dos Reis 2011-05-17 15:14:04 UTC --- (In reply to comment #6) > Double Sigh! I was hoping very few overloads would be enough... If we are > really talking about many I would be in favor of raising the issue, indeed. The issue is even trickier than that: If you were allowed to write those functions, what would begin() and end() return? a pointer into a soon-to-be-destroyed valarray? I think this is a defect in the standard. I just sent an email. -- Gaby