From: Ulrich Drepper <drepper.fsp@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Michael Levine <mlevine55@bloomberg.net>
Subject: Re: [committed v4] libstdc++: Fix std::ranges::iota is not included in numeric [PR108760]
Date: Sat, 8 Jun 2024 17:55:44 +0200 [thread overview]
Message-ID: <CAOPLpQd4hh45YOfwMQFgaUvFHoS+pUhg5ogywz=6drgX_k7bSQ@mail.gmail.com> (raw)
In-Reply-To: <20240608150555.457573-1-jwakely@redhat.com>
On Sat, Jun 8, 2024 at 5:03 PM Jonathan Wakely <jwakely@redhat.com> wrote:
> I'm in two minds about backporting this one. It would be good to fix the
> non-conformance problem for the release branches, but it also
> potentially breaks some code that uses ranges::iota without including
> <numeric>.
I say add the change as soon as possible so that there is as little
code as possible relying on the non-standard header.
next prev parent reply other threads:[~2024-06-08 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 18:24 [PATCH] " Michael Levine (BLOOMBERG/ 919 3RD A)
2024-04-18 21:58 ` Patrick Palka
2024-04-19 9:18 ` Jonathan Wakely
2024-05-17 16:59 ` [PATCH v2] libstdc++: Fix std::ranges::iota " Michael Levine (BLOOMBERG/ 731 LEX)
2024-05-23 22:41 ` Patrick Palka
2024-05-24 13:56 ` [PATCH v3] libstdc++: Fix std::ranges::iota not " Michael Levine (BLOOMBERG/ 731 LEX)
2024-05-24 14:12 ` Jonathan Wakely
2024-05-30 17:43 ` Michael Levine (BLOOMBERG/ 731 LEX)
2024-06-06 20:49 ` Michael Levine (BLOOMBERG/ 731 LEX)
2024-06-07 8:50 ` Jonathan Wakely
2024-06-08 15:03 ` [committed v4] libstdc++: Fix std::ranges::iota is not included " Jonathan Wakely
2024-06-08 15:55 ` Ulrich Drepper [this message]
2024-06-08 19:23 ` Jonathan Wakely
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='CAOPLpQd4hh45YOfwMQFgaUvFHoS+pUhg5ogywz=6drgX_k7bSQ@mail.gmail.com' \
--to=drepper.fsp@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mlevine55@bloomberg.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).