public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "valyala at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51981] New: Missing uninitialized_move() implementation? Date: Tue, 24 Jan 2012 17:34:00 -0000 [thread overview] Message-ID: <bug-51981-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51981 Bug #: 51981 Summary: Missing uninitialized_move() implementation? Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: valyala@gmail.com It's interesting to know why uninitialized_copy()'s counterpart - uninitialized_move() - is missing in http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/include/bits/stl_uninitialized.h?revision=177542&view=markup ? See boost's docs for details - http://www.boost.org/doc/libs/1_48_0/doc/html/boost/uninitialized_move.html .
next reply other threads:[~2012-01-24 16:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-24 17:34 valyala at gmail dot com [this message] 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
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@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).