public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/48635] [C++0x] unique_ptr<T, D&> moves the deleter instead of copying it Date: Sun, 17 Apr 2011 21:46:00 -0000 [thread overview] Message-ID: <bug-48635-4-Fet4PKKF1s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48635-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48635 --- Comment #9 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> 2011-04-17 21:46:15 UTC --- Author: paolo Date: Sun Apr 17 21:46:11 2011 New Revision: 172619 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172619 Log: 2011-04-17 Daniel Krugler <daniel.kruegler@googlemail.com> Paolo Carlini <paolo.carlini@oracle.com> PR libstdc++/48635 (again) * include/bits/unique_ptr.h (unique_ptr<>::unique_ptr(unique_ptr<>&&), unique_ptr<_Tp[]>::unique_ptr(unique_ptr<>&&), unique_ptr<>::operator=(unique_ptr<>&&), unique_ptr<_Tp[]>::operator=(unique_ptr<>&&)): Use forward<_Ep>, not forward<_Dp>, to forward the deleter. * testsuite/20_util/unique_ptr/assign/48635_neg.cc: New. Added: trunk/libstdc++-v3/testsuite/20_util/unique_ptr/assign/48635_neg.cc Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/bits/unique_ptr.h
next prev parent reply other threads:[~2011-04-17 21:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-15 21:01 [Bug libstdc++/48635] New: " daniel.kruegler at googlemail dot com 2011-04-15 21:46 ` [Bug libstdc++/48635] " daniel.kruegler at googlemail dot com 2011-04-16 0:25 ` paolo.carlini at oracle dot com 2011-04-16 0:58 ` paolo at gcc dot gnu.org 2011-04-16 1:01 ` paolo at gcc dot gnu.org 2011-04-16 1:01 ` paolo.carlini at oracle dot com 2011-04-17 19:18 ` daniel.kruegler at googlemail dot com 2011-04-17 19:45 ` paolo.carlini at oracle dot com 2011-04-17 20:12 ` daniel.kruegler at googlemail dot com 2011-04-17 21:46 ` paolo at gcc dot gnu.org [this message] 2011-04-17 21:47 ` paolo at gcc dot gnu.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-48635-4-Fet4PKKF1s@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).