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++/109024] [C++23][ranges][repeat_view] The default ctor unuseable
Date: Thu, 09 Mar 2023 18:37:45 +0000	[thread overview]
Message-ID: <bug-109024-4-z8AJekYHY7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109024-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109024

--- Comment #2 from CVS 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:065c93b89c5e97dcbfd79ee5172cf6800c286896

commit r13-6561-g065c93b89c5e97dcbfd79ee5172cf6800c286896
Author: Patrick Palka <ppalka@redhat.com>
Date:   Thu Mar 9 13:37:29 2023 -0500

    libstdc++: Implement LWG 3796 changes to repeat_/chunk_by_view [PR109024]

            PR libstdc++/109024

    libstdc++-v3/ChangeLog:

            * include/std/ranges (chunk_by_view::_M_pred): Remove DMI as per
            LWG 3796.
            (repeat_view::_M_pred): Likewise.
            * testsuite/std/ranges/adaptors/chunk_by/1.cc (test03): New test.
            * testsuite/std/ranges/repeat/1.cc (test05): New test.

  parent reply	other threads:[~2023-03-09 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 16:03 [Bug libstdc++/109024] New: " yronglin777 at gmail dot com
2023-03-06  1:05 ` [Bug libstdc++/109024] " de34 at live dot cn
2023-03-06 16:42 ` redi at gcc dot gnu.org
2023-03-08 15:55 ` ppalka at gcc dot gnu.org
2023-03-09 18:37 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-09 18:38 ` 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-109024-4-z8AJekYHY7@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: 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).