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 c++/101733] simple-requirement prefixed with typename interpreted as type-requirement
Date: Mon, 28 Nov 2022 20:52:53 +0000	[thread overview]
Message-ID: <bug-101733-4-qhpGssRU7Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101733-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:2b0ae7fb91f64fb005abf7d7903fd4c0764bb45c

commit r13-4380-g2b0ae7fb91f64fb005abf7d7903fd4c0764bb45c
Author: Jason Merrill <jason@redhat.com>
Date:   Sat Nov 26 11:13:55 2022 -0500

    c++: simple-requirement starting with 'typename' [PR101733]

    Usually a requirement starting with 'typename' is a type-requirement, but
it
    might be a simple-requirement such as a functional cast to a typename-type.

            PR c++/101733

    gcc/cp/ChangeLog:

            * parser.cc (cp_parser_requirement): Parse tentatively for the
            'typename' case.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/concepts-requires32.C: New test.

      parent reply	other threads:[~2022-11-28 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 19:17 [Bug c++/101733] New: " johelegp at gmail dot com
2021-08-02 19:49 ` [Bug c++/101733] " pinskia at gcc dot gnu.org
2022-10-18 12:39 ` redi at gcc dot gnu.org
2022-11-26 16:12 ` jason at gcc dot gnu.org
2022-11-28 20:52 ` cvs-commit at gcc dot gnu.org [this message]

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-101733-4-qhpGssRU7Y@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).