From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23468 invoked by alias); 13 Jan 2013 19:05:13 -0000 Received: (qmail 23288 invoked by uid 48); 13 Jan 2013 19:04:44 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/55963] std::vector fails Date: Sun, 13 Jan 2013 19:05:00 -0000 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: enhancement X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Severity 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 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: 2013-01/txt/msg01137.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55963 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement --- Comment #2 from Jonathan Wakely 2013-01-13 19:04:43 UTC --- I disagree with the claim it's required to work. It's true that container requirements have been relaxed so requirements on types are more fine-grained and only apply to specific operations, but std::vector instantiates std::allocator and that creates ambiguous overloads of std::allocator::address(reference) and std::allocator::address(const_reference) because reference and const_reference are the same type. I would argue it's required not to work, based on the explicit definition of std::allocator given in the C++11 standard. I've been thinking about altering std::allocator so it works though, so I'll confirm this as an extension.