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: Sat, 13 Jan 2024 04:02:52 +0000 [thread overview] Message-ID: <bug-108827-4-GGQzPuR83X@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 #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:ac1a399bf61b04845f5d6fc34e4b7a4db2bc5760 commit r14-7220-gac1a399bf61b04845f5d6fc34e4b7a4db2bc5760 Author: Patrick Palka <ppalka@redhat.com> Date: Fri Jan 12 23:02:12 2024 -0500 libstdc++: Implement C++23 std::bind_back from P2387R3 [PR108827] The implementation is based off of std::bind_front. Since this is a C++23 feature we use deducing this unconditionally. PR libstdc++/108827 PR libstdc++/111327 libstdc++-v3/ChangeLog: * include/bits/version.def (bind_back): Define. * include/bits/version.h: Regenerate. * include/std/functional (_Bind_back): Define for C++23. (bind_back): Likewise. * testsuite/20_util/function_objects/bind_back/1.cc: New test (adapted from corresponding bind_front test). * testsuite/20_util/function_objects/bind_back/111327.cc: Likewise.
next prev parent reply other threads:[~2024-01-13 4:02 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 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 [this message] 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-GGQzPuR83X@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).