From: Tom Tromey <tom@tromey.com>
To: Matthieu Longo <matthieu.longo@arm.com>
Cc: Andrew Burgess <aburgess@redhat.com>,
gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>,
Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
Luis Machado <luis.machado@amd.com>,
Luis Machado <luis.machado.foss@gmail.com>,
Christina Joos <christina.joos@intel.com>,
Kevin Buettner <kevinb@redhat.com>
Subject: Re: [PATCH v2 2/6] gdb support: add gdb::ranges::replace algorithm
Date: Wed, 16 Sep 2026 15:35:43 -0600 [thread overview]
Message-ID: <87ld906frk.fsf@tromey.com> (raw)
In-Reply-To: <206bab2e-27b4-4a59-8b11-f4a9a22c3128@arm.com> (Matthieu Longo's message of "Wed, 16 Sep 2026 17:03:40 +0100")
>>>>> "Matthieu" == Matthieu Longo <matthieu.longo@arm.com> writes:
Matthieu> #if __cplusplus >= 202002L
Matthieu> #error "replace the helpers below by the std::ranges::* equivalent."
Matthieu> #endif
Matthieu> in the file so that we don't forget about this and get rid of
Matthieu> it once GDB migrates to C++20. Is this ok ? Or to avoid ?
Probably avoid.
One thing we've done elsewhere is fall back to the std:: variant, via
aliases, if it's available.
You can also file a bug for this and have it block the C++20 meta-bug.
Tom
next prev parent reply other threads:[~2026-09-16 21:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 10:09 [PATCH v2 0/6] gdb: introduce file_reader_t to read procfs files Matthieu Longo
2026-08-25 10:09 ` [PATCH v2 1/6] target_fileio_read_stralloc: add an optional length parameter Matthieu Longo
2026-09-10 10:55 ` Andrew Burgess
2026-08-25 10:09 ` [PATCH v2 2/6] gdb support: add gdb::ranges::replace algorithm Matthieu Longo
2026-09-10 11:07 ` Andrew Burgess
2026-09-10 11:08 ` Andrew Burgess
2026-09-16 16:03 ` Matthieu Longo
2026-09-16 16:03 ` Matthieu Longo
2026-09-16 21:35 ` Tom Tromey [this message]
2026-08-25 10:09 ` [PATCH v2 3/6] gdb: introduce helper class file_reader_t Matthieu Longo
2026-09-10 15:35 ` Andrew Burgess
2026-08-25 10:09 ` [PATCH v2 4/6] gdb/linux-tdep: migrate linux_info_proc to file_reader_t Matthieu Longo
2026-09-10 16:31 ` Andrew Burgess
2026-08-25 10:09 ` [PATCH v2 5/6] gdb/linux-tdep: migrate linux_find_memory_regions_full " Matthieu Longo
2026-09-11 8:34 ` Andrew Burgess
2026-08-25 10:09 ` [PATCH v2 6/6] gdb/linux-tdep: remove legacy parse_smaps_data overload Matthieu Longo
2026-09-11 8:41 ` Andrew Burgess
2026-09-16 10:55 ` Matthieu Longo
2026-09-03 22:58 ` [PATCH v2 0/6] gdb: introduce file_reader_t to read procfs files Matthieu Longo
2026-09-08 10:27 ` Matthieu Longo
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=87ld906frk.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=christina.joos@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=luis.machado.foss@gmail.com \
--cc=luis.machado@amd.com \
--cc=matthieu.longo@arm.com \
--cc=simark@simark.ca \
--cc=thiago.bauermann@linaro.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