From: Paul Koning <paulkoning@comcast.net>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Minor doc fix for Python Type.fields
Date: Wed, 5 Nov 2025 14:30:35 -0500 [thread overview]
Message-ID: <5E6B1564-7155-4B31-A590-8A0FE95ED33F@comcast.net> (raw)
In-Reply-To: <877bw49t6j.fsf@tromey.com>
> On Nov 5, 2025, at 2:27 PM, Tom Tromey <tromey@adacore.com> wrote:
>
> Paul> My point is slightly different. No matter what sequence type is
> Paul> returned, for a given Type object the value of the sequence
> Paul> returned would be the same if you call that method twice, right?
>
> If gdb returns a memoized list, then modifications to the list will
> affect other calls. But, that would be undesirable.
>
> Tom
Yes, I wasn't thinking of someone modifying that value. I don't know a short expression for "tuple or new list".
Would it be hard to make it a tuple and not worry for now if it's memoized or not? That way you get the immutable property which makes sense to have.
paul
next prev parent reply other threads:[~2025-11-05 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 18:10 Tom Tromey
2025-11-05 18:29 ` Paul Koning
2025-11-05 19:05 ` Tom Tromey
2025-11-05 19:21 ` Paul Koning
2025-11-05 19:27 ` Tom Tromey
2025-11-05 19:30 ` Paul Koning [this message]
2025-11-05 19:30 ` Eli Zaretskii
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=5E6B1564-7155-4B31-A590-8A0FE95ED33F@comcast.net \
--to=paulkoning@comcast.net \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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