public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/43183] std::unique_ptr::reset() does not conform to N3035.
Date: Mon, 01 Mar 2010 16:09:00 -0000	[thread overview]
Message-ID: <20100301160852.5450.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43183-18834@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from paolo dot carlini at oracle dot com  2010-03-01 16:08 -------
Indeed, thanks Jon. Shall we implement this for 4.5.0, or we had better wait
for nullptr / nullptr_t, what do you think?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43183


  parent reply	other threads:[~2010-03-01 16:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 23:52 [Bug libstdc++/43183] New: " tjgolubi at netins dot net
2010-02-26  0:04 ` [Bug libstdc++/43183] " paolo dot carlini at oracle dot com
2010-02-26  0:13 ` paolo dot carlini at oracle dot com
2010-02-26  0:16 ` paolo dot carlini at oracle dot com
2010-02-26 18:04 ` paolo dot carlini at oracle dot com
2010-03-01 15:05 ` jwakely dot gcc at gmail dot com
2010-03-01 16:09 ` paolo dot carlini at oracle dot com [this message]
2010-03-01 16:24 ` jwakely dot gcc at gmail dot com
2010-03-01 16:35 ` jwakely dot gcc at gmail dot com
2010-03-01 17:06 ` paolo dot carlini at oracle dot com
2010-03-01 20:56 ` redi at gcc dot gnu dot org
2010-03-01 22:22 ` tjgolubi at netins dot net
2010-03-01 22:31 ` redi at gcc dot gnu dot org
2010-03-01 22:38 ` redi at gcc dot gnu dot org
2010-03-01 23:23 ` tjgolubi at netins dot net
2010-03-02  0:41 ` redi at gcc dot gnu dot org
2010-03-02  0:42 ` redi at gcc dot gnu dot org
2010-03-02 11:41 ` jwakely dot gcc at gmail dot com
2010-03-02 12:44 ` jwakely dot gcc at gmail dot com

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=20100301160852.5450.qmail@sourceware.org \
    --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: link
Be 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).