public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51981] Missing uninitialized_move() implementation? Date: Wed, 25 Jan 2012 15:34:00 -0000 [thread overview] Message-ID: <bug-51981-4-HGHmhdWMX0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51981-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51981 --- Comment #5 from Marc Glisse <marc.glisse at normalesup dot org> 2012-01-25 15:02:55 UTC --- (In reply to comment #3) > (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. I don't think novices should use anything with "uninitialized" in the name. Notice that very few functions on iterators have a move version. vector::insert doesn't come with a move_insert counterpart. > If continuing in this vein, then std::move() can be substituted by std::copy() > with input iterator wrapped into make_move_iterator(). True, although there can be subtle differences for input iterators where the reference type is not a reference to the value_type (there's a DR about that). > Then std::move() is not so useful :) Indeed. The standard tries to keep a balance, and I guess move was considered common enough to deserve its own interface, but could easily have been removed. Note that I don't think gcc's bugzilla is the best place for such discussions...
prev parent reply other threads:[~2012-01-25 15:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-24 17:34 [Bug libstdc++/51981] New: " valyala at gmail dot com 2012-01-24 17:42 ` [Bug libstdc++/51981] " redi at gcc dot gnu.org 2012-01-25 0:03 ` marc.glisse at normalesup dot org 2012-01-25 14:59 ` valyala at gmail dot com 2012-01-25 15:31 ` paolo.carlini at oracle dot com 2012-01-25 15:34 ` marc.glisse at normalesup dot org [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-51981-4-HGHmhdWMX0@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).