From: Simon Marchi <simon.marchi@efficios.com>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb: make gdbarch_displaced_step_copy_insn return an std::unique_ptr
Date: Fri, 14 Feb 2020 20:31:00 -0000 [thread overview]
Message-ID: <ab21b700-a5b8-f0a3-85ef-7ee06d9dbd9d@efficios.com> (raw)
In-Reply-To: <afd78d9b-9604-543b-e67a-dc7217056688@redhat.com>
On 2020-02-14 2:48 p.m., Pedro Alves wrote:
> BTW, when I see a bunch of std::unique_ptr<footype>
> I wonder whether a footype_up typedef wouldn't make things
> read a bit clearer.
Personally I don't mind the explicit std::unique_ptr<footype>,
unless we're starting to use containers of that type. I then prefer:
std::vector<footype_up>
over
std::vector<std::unique_ptr<footype>>
But I also don't mind using a typedef either, even without using containers,
so I'll do that change as a separate patch on top.
Thanks for the review!
Simon
next prev parent reply other threads:[~2020-02-14 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 15:14 [PATCH 1/2] gdb: cleanup of displaced_step_inferior_state::reset/displaced_step_clear Simon Marchi
2020-01-22 15:20 ` [PATCH 2/2] gdb: make gdbarch_displaced_step_copy_insn return an std::unique_ptr Simon Marchi
2020-02-14 19:47 ` Pedro Alves
2020-02-14 19:48 ` Pedro Alves
2020-02-14 20:31 ` Simon Marchi [this message]
2020-02-13 22:52 ` [PATCH 1/2] gdb: cleanup of displaced_step_inferior_state::reset/displaced_step_clear Simon Marchi
2020-02-14 19:39 ` Pedro Alves
2020-02-14 20:11 ` Simon Marchi
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=ab21b700-a5b8-f0a3-85ef-7ee06d9dbd9d@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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