public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
	Patrick Palka <ppalka@redhat.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH 2/2] libstdc++: Implement range_adaptor_closure from P2387R3 [PR108827]
Date: Tue, 18 Apr 2023 10:59:53 +0200	[thread overview]
Message-ID: <ZD5cCeZloLzBVqlh@tucnak> (raw)
In-Reply-To: <CACb0b4kAjORe9anH=gkp1pWvoKxyofizUCHAoR2rZHbiixPwug@mail.gmail.com>

On Tue, Apr 18, 2023 at 09:57:19AM +0100, Jonathan Wakely wrote:
> On Mon, 17 Apr 2023 at 08:26, Jonathan Wakely via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
> >
> > On Mon, 17 Apr 2023, 05:28 Patrick Palka via Libstdc++, <
> > libstdc++@gcc.gnu.org> wrote:
> >
> > > On Fri, 14 Apr 2023, Patrick Palka wrote:
> > >
> > > > Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
> > > >
> > > >       PR libstdc++/108827
> > > >
> > > > libstdc++-v3/ChangeLog:
> > > >
> > > >       * include/bits/ranges_cmp.h (__cpp_lib_ranges): Bump value
> > > >       for C++23.
> > > >       * include/std/ranges (range_adaptor_closure): Define for C++23.
> > > >       * include/std/version (__cpp_lib_ranges): Bump value for
> > > >       C++23.
> > > >       * testsuite/std/ranges/version_c++23.cc: Bump expected value
> > > >       of __cpp_lib_ranges.
> > > >       * testsuite/std/ranges/range_adaptor_closure.cc: New test.
> > >
> > > Here's a standalone version of this patch (not dependent on the first
> > > patch in the series) it terms of the current non-CRTP representation
> > > of _RangeAdaptorClosure:
> > >
> >
> > OK, thanks for separating this from the other change.
> 
> I'd like RM approval to push this C++23-only change to gcc-13 as well as trunk.

Ok.

	Jakub


  reply	other threads:[~2023-04-18  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 19:45 [PATCH 1/2] libstdc++: Convert _RangeAdaptorClosure into a CRTP class [PR108827] Patrick Palka
2023-04-14 19:45 ` [PATCH 2/2] libstdc++: Implement range_adaptor_closure from P2387R3 [PR108827] Patrick Palka
2023-04-17  3:27   ` Patrick Palka
2023-04-17  7:26     ` Jonathan Wakely
2023-04-18  8:57       ` Jonathan Wakely
2023-04-18  8:59         ` Jakub Jelinek [this message]
2023-04-17  3:24 ` [PATCH 1/2] libstdc++: Convert _RangeAdaptorClosure into a CRTP class [PR108827] Patrick Palka
2023-08-16 16:05   ` Patrick Palka
2023-08-16 17:32     ` 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=ZD5cCeZloLzBVqlh@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ppalka@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).