public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108827] [C++23] Implement P2387R3, Pipe support for user-defined range adaptors Date: Tue, 18 Apr 2023 11:28:44 +0000 [thread overview] Message-ID: <bug-108827-4-tW92ZjO4Q1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108827-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108827 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:769c324424500a3d20de7417f62a4e7bce345775 commit r13-7214-g769c324424500a3d20de7417f62a4e7bce345775 Author: Patrick Palka <ppalka@redhat.com> Date: Tue Apr 18 07:21:13 2023 -0400 libstdc++: Implement range_adaptor_closure from P2387R3 [PR108827] 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. (cherry picked from commit cb5c71d16d0fb47638498365f5c857ce7c673eaf)
next prev parent reply other threads:[~2023-04-18 11:28 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-16 18:05 [Bug libstdc++/108827] New: " ppalka at gcc dot gnu.org 2023-02-16 23:28 ` [Bug libstdc++/108827] " redi at gcc dot gnu.org 2023-04-18 11:23 ` cvs-commit at gcc dot gnu.org 2023-04-18 11:28 ` cvs-commit at gcc dot gnu.org [this message] 2023-08-17 16:40 ` cvs-commit at gcc dot gnu.org 2023-09-07 12:51 ` redi at gcc dot gnu.org 2024-01-13 4:02 ` cvs-commit at gcc dot gnu.org 2024-01-13 4:06 ` ppalka at gcc dot gnu.org
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=bug-108827-4-tW92ZjO4Q1@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).