public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107168] New: Wrong errors for concepts with default lambda not-type argument
Date: Thu, 06 Oct 2022 07:08:01 +0000	[thread overview]
Message-ID: <bug-107168-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107168
           Summary: Wrong errors for concepts with default lambda not-type
                    argument
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fchelnokov at gmail dot com
  Target Milestone: ---

The following code in accepted in Clang and MSVC, but GCC emits seemingly wrong
errors:

template <typename, auto = []{}> concept x = true;
struct S {
    // GCC error: template argument 2 is invalid
    operator x auto() { return 42; }
    // GCC error: wrong number of template arguments (0, should be at least 1)
    operator x<> auto() const { return 43; }
};

Online demo: https://godbolt.org/z/a3494qrG3

             reply	other threads:[~2022-10-06  7:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06  7:08 fchelnokov at gmail dot com [this message]
2022-10-06 11:01 ` [Bug c++/107168] [11/12/13 Regression] Wrong errors for concepts with default lambda not-type argument since r11-3714-gc1c62aec6751678e marxin at gcc dot gnu.org
2023-03-09 22:15 ` jason at gcc dot gnu.org
2024-01-12 10:06 ` [Bug c++/107168] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-04-13 20:52 ` [Bug c++/107168] [11/12/13 " pinskia at gcc dot gnu.org
2024-04-15 15: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-107168-4@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).