From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Introduce gdb::unique_ptr
Date: Fri, 14 Oct 2016 16:11:00 -0000 [thread overview]
Message-ID: <09c955e2-8c9c-8dd7-67fe-cbc83c3cfa2e@redhat.com> (raw)
In-Reply-To: <4c97e05492f34198bb6cafc860bbdbc8@simark.ca>
On 10/14/2016 05:07 PM, Simon Marchi wrote:
> On 2016-10-14 08:50, Pedro Alves wrote:
>> +struct unique_ptr_nullptr_t
>> +{
>> +private:
>> + struct private_type;
>> +public:
>> + /* Since null_type is private, the only way to construct this class
>
> null_type, or private_type?
Whoops, yes, private_type. Used to be called null_type, but then
I renamed it thinking that it'd be clearer.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-14 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 12:29 [PATCH v2] " Pedro Alves
2016-10-14 12:50 ` [PATCH v3] " Pedro Alves
2016-10-14 16:07 ` Simon Marchi
2016-10-14 16:11 ` Pedro Alves [this message]
2016-10-14 16:31 ` Pedro Alves
2016-10-16 7:14 ` Tom Tromey
2016-10-17 13:51 ` [PATCH v4] " Pedro Alves
2016-10-17 18:00 ` Buildslaves and C++11 support Pedro Alves
2016-10-17 23:20 ` Pedro Alves
2016-10-19 3:23 ` John Baldwin
2016-10-19 12:50 ` Pedro Alves
2016-10-18 2:33 ` [PATCH v4] Introduce gdb::unique_ptr Tom Tromey
2016-10-18 10:45 ` Pedro Alves
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=09c955e2-8c9c-8dd7-67fe-cbc83c3cfa2e@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).