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++/111055] [C++23] Implement P1206R7, Conversions from ranges to containers Date: Thu, 23 Nov 2023 17:51:11 +0000 [thread overview] Message-ID: <bug-111055-4-RRGJfRnBIQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111055-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111055 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:7a6a29c455e7755b501c0006e39beb4e56ec2729 commit r14-5794-g7a6a29c455e7755b501c0006e39beb4e56ec2729 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Sep 19 13:23:13 2023 +0100 libstdc++: Define std::ranges::to for C++23 (P1206R7) [PR111055] This adds the std::ranges::to functions for C++23. The rest of P1206R7 is not yet implemented, i.e. the new constructors taking the std::from_range tag, and the new insert_range, assign_range, etc. member functions. std::ranges::to works with the standard containers even without the new constructors, so this is useful immediately. The __cpp_lib_ranges_to_container feature test macro can be defined now, because that only indicates support for the changes in <ranges>, which are implemented by this patch. The __cpp_lib_containers_ranges macro will be defined once all containers support the new member functions. libstdc++-v3/ChangeLog: PR libstdc++/111055 * include/bits/ranges_base.h (from_range_t): Define new tag type. (from_range): Define new tag object. * include/bits/version.def (ranges_to_container): Define. * include/bits/version.h: Regenerate. * include/std/ranges (ranges::to): Define. * testsuite/std/ranges/conv/1.cc: New test. * testsuite/std/ranges/conv/2_neg.cc: New test. * testsuite/std/ranges/conv/version.cc: New test.
next prev parent reply other threads:[~2023-11-23 17:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-17 22:03 [Bug libstdc++/111055] New: " redi at gcc dot gnu.org 2023-08-17 22:04 ` [Bug libstdc++/111055] " redi at gcc dot gnu.org 2023-09-18 17:19 ` redi at gcc dot gnu.org 2023-09-19 12:27 ` redi at gcc dot gnu.org 2023-11-23 17:51 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-23 17:54 ` redi 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-111055-4-RRGJfRnBIQ@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).