From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/4] Add gdbpy_borrowed_ref
Date: Thu, 21 May 2026 15:01:24 -0600 [thread overview]
Message-ID: <87jyswjx3v.fsf@tromey.com> (raw)
In-Reply-To: <87cxyuclhd.fsf@redhat.com> (Andrew Burgess's message of "Sun, 17 May 2026 12:40:46 +0100")
>> This adds new gdbpy_opt_borrowed_ref and gdbpy_borrowed_ref classes.
>> These class is primarily for code "documentation" purposes -- it makes
Andrew> type: These CLASSES ARE primarily ....
Fixed.
Andrew> Could/should this be marked as 'const'?
Yeah, plus the other ones you pointed out.
>> + /* Allow a (checked) conversion to any subclass of PyObject. */
>> + template<typename T,
>> + typename = std::is_convertible<T *, PyObject *>>
>> + operator T * ()
>> + {
>> + gdb_assert (PyObject_TypeCheck (m_obj, T::corresponding_object_type));
>> + return static_cast<T *> (m_obj);
>> + }
Andrew> OK, please excuse my ignorance here, I might be completely wrong, but I
Andrew> believe the line 'typename = std::is_convertible<T *, PyObject *>' is
Andrew> here for the purpose of SFINAE. I believe this was copied from
Andrew> gdb_ref_ptr.h, but I think this line might be wrong, both there and
Andrew> here.
Yep, oops.
I fixed this here & sent a separate patch for gdb_ref_ptr.h.
Tom
next prev parent reply other threads:[~2026-05-21 21:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 19:59 [PATCH v2 0/4] Python safety initial work Tom Tromey
2026-05-15 19:59 ` [PATCH v2 1/4] Add gdbpy_borrowed_ref Tom Tromey
2026-05-17 11:40 ` Andrew Burgess
2026-05-21 17:48 ` Tom Tromey
2026-05-21 21:01 ` Tom Tromey [this message]
2026-05-15 19:59 ` [PATCH v2 2/4] Add wrappers for some Python APIs Tom Tromey
2026-05-17 12:06 ` Andrew Burgess
2026-05-21 21:05 ` Tom Tromey
2026-05-15 19:59 ` [PATCH v2 3/4] Add wrappers for Python implementation functions and methods Tom Tromey
2026-05-18 9:33 ` Andrew Burgess
2026-05-21 21:23 ` Tom Tromey
2026-05-18 10:00 ` Andrew Burgess
2026-05-21 22:41 ` Tom Tromey
2026-05-29 15:58 ` Andrew Burgess
2026-05-15 19:59 ` [PATCH v2 4/4] Convert py-tui.c to the "python safety" approach Tom Tromey
2026-05-18 12:39 ` Andrew Burgess
2026-05-21 21:21 ` 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=87jyswjx3v.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/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