From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-175773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 21144 invoked by alias); 6 Feb 2006 15:34:39 -0000
Received: (qmail 21129 invoked by uid 48); 6 Feb 2006 15:34:36 -0000
Date: Mon, 06 Feb 2006 15:34:00 -0000
Subject: [Bug libstdc++/26133]  New: unique_copy requires assignability when using output iterators
X-Bugzilla-Reason: CC
Message-ID: <bug-26133-11044@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "squell at alumina dot nl" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2006-02/txt/msg00519.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

unique_copy is overloaded on forward- and output_iterators for the result
iterator; the output_iterator version requires Assignability on the input's
value_type, which isn't required by the resolution to DR #241:

http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#241

I'll attach a demonstration, which compiles on at least one other
implementation. When using only input AND only output iterators,
implementations must keep a temporary copy somewhere; is the standard implying
that implementations use placement new for that?


-- 
           Summary: unique_copy requires assignability when using output
                    iterators
           Product: gcc
           Version: 4.0.1
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: squell at alumina dot nl


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26133