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: Patrick Palka <ppalka@redhat.com>,
	gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Adding missing feature-test macros for C++23 ranges algos
Date: Tue, 18 Apr 2023 10:59:12 +0200	[thread overview]
Message-ID: <ZD5b4AwPQdElk6+s@tucnak> (raw)
In-Reply-To: <CACb0b4mrBaLbU02BdW6GmPGcaL-OLkP_3FZk+BLoRv-q5hcxXQ@mail.gmail.com>

On Tue, Apr 18, 2023 at 09:56:33AM +0100, Jonathan Wakely wrote:
> On Mon, 17 Apr 2023 at 04:46, Patrick Palka via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
> >
> > This patch also renames __cpp_lib_fold to __cpp_lib_ranges_fold
> > as per the current draft standard.
> 
> OK, but this needs RM approval to push to gcc-13

Ok, if you can commit it today.

> > libstdc++-v3/ChangeLog:
> >
> >         * include/bits/ranges_algo.h (__cpp_lib_ranges_contains):
> >         Define for C++23.
> >         (__cpp_lib_ranges_iota): Likewise.
> >         (__cpp_lib_ranges_find_last): Likewise.
> >         (__cpp_lib_fold): Rename to ...
> >         (__cpp_lib_ranges_fold): ... this.
> >         * include/std/version: As above.
> >         * testsuite/25_algorithms/fold_left/1.cc: Adjust after
> >         renaming __cpp_lib_fold.
> >         * testsuite/std/ranges/version_c++23.cc: Verify values
> >         of the above feature-test macros.

	Jakub


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17  3:45 Patrick Palka
2023-04-18  8:56 ` Jonathan Wakely
2023-04-18  8:59   ` Jakub Jelinek [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=ZD5b4AwPQdElk6+s@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).