From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Update use of deque in _frame_iterator
Date: Mon, 22 Jun 2026 16:16:03 -0600 [thread overview]
Message-ID: <8733yei5lo.fsf@tromey.com> (raw)
In-Reply-To: <20260603002639.3920962-1-tom@tromey.com> (Tom Tromey's message of "Tue, 2 Jun 2026 18:26:39 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> _frame_iterator has an old comment about some hand-written code that
Tom> was needed when supporting Python 2.6. This patch simplifies the code
Tom> by using a couple of features of collections.deque.
I'm checking this in now.
Tom
prev parent reply other threads:[~2026-06-22 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 0:26 Tom Tromey
2026-06-22 22:16 ` Tom Tromey [this message]
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=8733yei5lo.fsf@tromey.com \
--to=tom@tromey.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