This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51981] Missing uninitialized_move() implementation?
- From: "valyala at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 25 Jan 2012 14:38:50 +0000
- Subject: [Bug libstdc++/51981] Missing uninitialized_move() implementation?
- Auto-submitted: auto-generated
- References: <bug-51981-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51981
--- Comment #3 from Aliaksandr Valialkin <valyala at gmail dot com> 2012-01-25 14:38:50 UTC ---
(In reply to comment #2)
> It looks like it would be equivalent to uninitialized_copy with
> make_move_iterator, not so useful then.
This makes sense, but not so obvious for novices in C++11.
If continuing in this vein, then std::move() can be substituted by std::copy()
with input iterator wrapped into make_move_iterator(). Then std::move() is not
so useful :)