From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA v2 1/7] Remove some ui_out-related cleanups from Python
Date: Fri, 10 Feb 2017 19:18:00 -0000 [thread overview]
Message-ID: <871sv526tl.fsf@tromey.com> (raw)
In-Reply-To: <e71cf655386810ace74b036a04a3c17f@polymtl.ca> (Simon Marchi's message of "Fri, 10 Feb 2017 10:57:09 -0500")
>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
Simon> I am curious what are the differences between using an
Simon> std::optional and a std::unique_ptr.
[...]
Simon> The obvious one is stack memory allocation for optional and heap for
Simon> unique_ptr, but apart from that, any difference in the functionality?
No, they're basically equivalent.
Tom
next prev parent reply other threads:[~2017-02-10 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 21:25 [RFA v2 0/7] more cleanup removal in Python Tom Tromey
2017-02-09 21:25 ` [RFA v2 6/7] Remove unnecessary local variables Tom Tromey
2017-02-09 21:25 ` [RFA v2 3/7] Use gdbpy_ref to simplify some logic Tom Tromey
2017-02-09 21:25 ` [RFA v2 5/7] Remove some gotos from Python Tom Tromey
2017-02-09 21:25 ` [RFA v2 7/7] Fix Python test to use lowercase command Tom Tromey
2017-02-09 21:25 ` [RFA v2 1/7] Remove some ui_out-related cleanups from Python Tom Tromey
2017-02-10 15:57 ` Simon Marchi
2017-02-10 19:18 ` Tom Tromey [this message]
2017-02-09 21:25 ` [RFA v2 4/7] Change one more spot to use gdbpy_ref Tom Tromey
2017-02-09 21:25 ` [RFA v2 2/7] Turn gdbpy_ref into a template Tom Tromey
2017-02-10 16:21 ` [RFA v2 0/7] more cleanup removal in Python Simon Marchi
2017-02-10 16:36 ` Pedro Alves
2017-02-10 19:18 ` Tom Tromey
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=871sv526tl.fsf@tromey.com \
--to=tom@tromey.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).