From: Simon Marchi <simon.marchi@efficios.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] gdbsupport: make filtered_iterator work with pointers
Date: Fri, 29 Aug 2025 12:00:56 -0400 [thread overview]
Message-ID: <c89feed5-9fdc-4a4e-9cda-870eb08df21c@efficios.com> (raw)
In-Reply-To: <875xe6utyx.fsf@tromey.com>
On 2025-08-29 09:40, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
>
> Simon> It's currently not possible to use filtered_iterator with a pointer as
> Simon> the base iterator type. This patch makes it possible.
>
> I have a question about the forwarding constructor.
>
> Simon> + using iterator_category =
> Simon> + typename std::iterator_traits<BaseIterator>::iterator_category;
> Simon> + ;
> Simon> + using difference_type =
> Simon> + typename std::iterator_traits<BaseIterator>::difference_type;
> Simon> + ;
>
> Couple of random ";" there.
Oops, thanks, assignment operators were misplaced too.
> Simon> @@ -44,6 +46,10 @@ class filtered_iterator
> Simon> : m_it (std::forward<Args> (args)...)
> Simon> { skip_filtered (); }
>
> It seems to me that the presence of this constructor means that some
> existing code could change meaning. It's not really likely but I wonder
> how we would know.
Yeah, you're right. For the meaning of a call site to change, that call
site would need:
- a BaseIterator that can be constructed from two arguments A and B
(the existing constructor of filtered_iterator would then be called)
- that same BaseIterator can be constructed from the single argument A, and
also from the single argument B (the new constructor of
filtered_iterator would then be called)
I don't know how to know for sure whether this happens.
> I also wonder what this constructor is even needed for since it seems
> like a filtered iterator should just wrap an ordinary one anyway.
I think it's just a shortcut to have less boilerplate when you need to
instantiate a filtered_iterator. I think I would prefer having just the
begin/end version, so that there is less magic involved, making it
easier to debug compilation errors, at the expense of having to be more
explicit at the call sites. I think I tried it in a previous iteration
of this series and gave up, but if you think it's a good idea, I can try
it again.
Simon
next prev parent reply other threads:[~2025-08-29 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 15:10 [PATCH 1/3] gdb/objfiles: make objfile::sections yield references Simon Marchi
2025-08-28 15:10 ` [PATCH 2/3] gdbsupport: make filtered_iterator work with pointers Simon Marchi
2025-08-29 13:40 ` Tom Tromey
2025-08-29 16:00 ` Simon Marchi [this message]
2025-08-29 17:39 ` Tom Tromey
2025-08-29 20:11 ` Simon Marchi
2025-09-03 2:01 ` Tom Tromey
2025-08-29 17:59 ` Simon Marchi
2025-08-29 18:19 ` Tom Tromey
2025-08-28 15:10 ` [PATCH 3/3] gdb/objfiles: use filtered_iterator as objfile::section_iterator Simon Marchi
2025-08-29 13:42 ` Tom Tromey
2025-08-29 16:06 ` Simon Marchi
2025-08-29 20:22 ` Simon Marchi
2025-08-29 13:34 ` [PATCH 1/3] gdb/objfiles: make objfile::sections yield references Tom Tromey
2025-08-29 15:47 ` 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=c89feed5-9fdc-4a4e-9cda-870eb08df21c@efficios.com \
--to=simon.marchi@efficios.com \
--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