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++/108362] views::istream is SFINAE-unfriendly
Date: Sat, 29 Apr 2023 14:04:05 +0000	[thread overview]
Message-ID: <bug-108362-4-sv9db4lTyj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108362-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:7d0cddced0ff101f5f59ceb2a45e7f145ff973ac

commit r12-9496-g7d0cddced0ff101f5f59ceb2a45e7f145ff973ac
Author: Patrick Palka <ppalka@redhat.com>
Date:   Thu Mar 9 13:35:04 2023 -0500

    libstdc++: Make views::single/iota/istream SFINAE-friendly [PR108362]

            PR libstdc++/108362

    libstdc++-v3/ChangeLog:

            * include/std/ranges (__detail::__can_single_view): New concept.
            (_Single::operator()): Constrain it.  Move [[nodiscard]] to the
            end of the function declarator.
            (__detail::__can_iota_view): New concept.
            (_Iota::operator()): Constrain it.  Move [[nodiscard]] to the
            end of the function declarator.
            (__detail::__can_istream_view): New concept.
            (_Istream::operator()): Constrain it.  Move [[nodiscard]] to the
            end of the function declarator.
            * testsuite/std/ranges/iota/lwg3292_neg.cc: Prune "in
            requirements" diagnostic.
            * testsuite/std/ranges/iota/iota_view.cc (test07): New test.
            * testsuite/std/ranges/istream_view.cc (test08): New test.
            * testsuite/std/ranges/single_view.cc (test07): New test.

    (cherry picked from commit 95827e1b9f7d5dd5a697bd60292e3876a7e8c15c)

  parent reply	other threads:[~2023-04-29 14:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 15:24 [Bug libstdc++/108362] New: " hewillk at gmail dot com
2023-01-13  0:19 ` [Bug libstdc++/108362] " redi at gcc dot gnu.org
2023-03-07 21:04 ` ppalka at gcc dot gnu.org
2023-03-09 18:35 ` cvs-commit at gcc dot gnu.org
2023-03-09 18:35 ` ppalka at gcc dot gnu.org
2023-04-29 14:04 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-29 14:05 ` 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-108362-4-sv9db4lTyj@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).