From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id D2C583858C50; Fri, 30 Aug 2024 10:43:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D2C583858C50
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1725014632;
	bh=I0BWEba2pPB46HD7WO99GAbp33LGbMwOOeBaCeFN4gc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Tjnm1STD+Bk77iruyrw7dkmbAfx/8sKAstoSbS6IdoSA6NAVQguED8BB5xuZvdox9
	 HVvn/EYxGMgfvRA3tVAxqlm3EDERbL9eq9ssA0OpkPj9KpFDe7smFKEMEI6qKCnMGL
	 9/wubuhv/eR+6r+4H2snBXRigFDvxR1+u6w4vebg=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/116529] Construction of unique_ptr with reference
 type is rejected because of auto_ptr constructor
Date: Fri, 30 Aug 2024 10:43:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 15.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-116529-4-l6TsWsTdk6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-116529-4@http.gcc.gnu.org/bugzilla/>
References: <bug-116529-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D116529

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Do you have an actual use case for this, or are you just reporting it becau=
se
there's divergence between implementations?

I raised it with the standards committee and everybody agrees that we should
not support this, so I'm creating a new library issue for it.=