This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51609] [C++11] unique_ptr<const T[]>::reset rejects cv-compatible argument pointers
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 19 Dec 2011 02:24:24 +0000
- Subject: [Bug libstdc++/51609] [C++11] unique_ptr<const T[]>::reset rejects cv-compatible argument pointers
- Auto-submitted: auto-generated
- References: <bug-51609-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51609
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-12-19 02:24:24 UTC ---
While I agree the code is reasonable, I think an LWG issue is needed, because I
don't think GCC's behaviour is in conflict with the standard.
I don't read [unique.ptr.runtime] p1 b2 as requiring that cv-qualified types
must be accepted. It only says types derived from T are rejected, which GCC
does.
The standard defines exactly these overloads:
void reset(pointer p = pointer()) noexcept;
void reset(nullptr_t) noexcept;
template <class U> void reset(U) = delete;
and there is nothing in [unique.ptr.runtime.modiïers] to constrain the
template.