This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/70472] is_copy_constructible<vector<unique_ptr<int>>>::value is true
- From: "rs2740 at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 18 Apr 2016 20:38:56 +0000
- Subject: [Bug libstdc++/70472] is_copy_constructible<vector<unique_ptr<int>>>::value is true
- Auto-submitted: auto-generated
- References: <bug-70472-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70472
TC <rs2740 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rs2740 at gmail dot com
--- Comment #5 from TC <rs2740 at gmail dot com> ---
In any event, it would be wrong to SFINAE on
std::is_copy_constructible<value_type>. The requirement is CopyInsertable, not
CopyConstructible. The allocator's construct() can mutilate the constructor
arguments to its heart's content before passing them on, and I don't see a way
to check this.