From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFC 0/4] Better Python safety
Date: Tue, 24 Feb 2026 09:29:43 -0700 [thread overview]
Message-ID: <877bs2w1e0.fsf@tromey.com> (raw)
In-Reply-To: <14087536-5ab7-48f7-a10f-30cf0a016254@simark.ca> (Simon Marchi's message of "Mon, 23 Feb 2026 20:05:42 -0500")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
>> gdbpy_optional_ref is used for keyword arguments and also by setters.
>> Not sure if it will see any other uses.
Simon> Is this kind of ref also borrowed? If so I would include "borrowed" in
Simon> its name, otherwise it's confusing. Perhaps gdbpy_opt_borrowed_ref? Or
Simon> flip the naming around, make the "default" borrowed and find a name for
Simon> the "strong" refs.
Yeah, it is also borrowed. I can rename it easily enough.
I think it's fine for optionally-borrowed-ref to have a longer name
since this concept is barely used.
Tom
next prev parent reply other threads:[~2026-02-24 16:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 19:49 Tom Tromey
2026-02-22 19:49 ` [RFC 1/4] Add gdbpy_borrowed_ref Tom Tromey
2026-02-24 4:57 ` Simon Marchi
2026-02-25 3:55 ` Tom Tromey
2026-02-25 15:24 ` Simon Marchi
2026-02-26 1:38 ` Tom Tromey
2026-02-22 19:49 ` [RFC 2/4] Add wrappers for some Python APIs Tom Tromey
2026-02-22 19:49 ` [RFC 3/4] Add constexpr functions to create PyMethodDef entries Tom Tromey
2026-02-22 19:49 ` [RFC 4/4] Convert some Python code to new-style Tom Tromey
2026-02-23 20:28 ` [RFC 0/4] Better Python safety Simon Marchi
2026-02-23 21:00 ` Simon Marchi
2026-02-23 23:23 ` Tom Tromey
2026-02-23 23:56 ` Tom Tromey
2026-02-24 1:05 ` Simon Marchi
2026-02-24 16:29 ` Tom Tromey [this message]
2026-02-23 21:22 ` Tom Tromey
2026-03-04 17:39 ` Matthieu Longo
2026-03-04 21:02 ` 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=877bs2w1e0.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.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