From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/4] gdb: constify parameter of value_copy
Date: Sun, 6 Mar 2022 11:33:49 -0500 [thread overview]
Message-ID: <ddd8380a-c023-80ab-4115-d26170460142@polymtl.ca> (raw)
In-Reply-To: <87fsnxu20i.fsf@tromey.com>
On 2022-03-04 11:16, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Simon> In a following patch, I have a const value I want to copy using a
> Simon> value_copy. However, value_copy takes a non-const source value, at the
> Simon> moment. Change the paramter to be const,
>
> This seems like a reasonable cleanup that could go in immediately.
>
> Tom
Done.
Simon
next prev parent reply other threads:[~2022-03-06 16:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 14:07 [PATCH 0/4] Add variant type Simon Marchi
2022-02-01 14:07 ` [PATCH 1/4] gdb: remove internalvar_funcs::destroy Simon Marchi
2022-03-04 16:15 ` Tom Tromey
2022-03-06 16:33 ` Simon Marchi
2022-02-01 14:07 ` [PATCH 2/4] gdb: constify parameter of value_copy Simon Marchi
2022-03-04 16:16 ` Tom Tromey
2022-03-06 16:33 ` Simon Marchi [this message]
2022-02-01 14:07 ` [PATCH 3/4] gdbsupport: add variant-lite header Simon Marchi
2022-02-01 14:07 ` [PATCH 4/4] gdb: make internalvar use a variant Simon Marchi
2022-03-04 16:23 ` Tom Tromey
2022-03-07 12:12 ` Pedro Alves
2022-03-16 2:06 ` Simon Marchi
2022-03-16 13:26 ` Pedro Alves
2022-03-16 13:28 ` Simon Marchi
2022-02-03 0:02 ` [PATCH 0/4] Add variant type Andrew Burgess
2022-02-03 1:32 ` Simon Marchi
2022-02-04 12:44 ` Andrew Burgess
2022-02-04 13:19 ` 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=ddd8380a-c023-80ab-4115-d26170460142@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).