public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "enolan at alumni dot cmu.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103593] New: Naming the constructor of a template class without using the injected-class-name causes parse error with C++20
Date: Mon, 06 Dec 2021 22:32:21 +0000	[thread overview]
Message-ID: <bug-103593-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103593
           Summary: Naming the constructor of a template class without
                    using the injected-class-name causes parse error with
                    C++20
           Product: gcc
           Version: 11.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: enolan at alumni dot cmu.edu
  Target Milestone: ---

This seems to be a GCC 11/12 regression.

https://godbolt.org/z/vTPs9reTW

Flags: -std=c++20

Code:

```
template <typename T>
class Foo {
public:
  Foo<T>();
};
```

Result:

```
<source>:4:10: error: expected unqualified-id before ')' token
    4 |   Foo<T>();
      |          ^
```

             reply	other threads:[~2021-12-06 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 22:32 enolan at alumni dot cmu.edu [this message]
2021-12-06 22:42 ` [Bug c++/103593] [11/12 Regression] " pinskia at gcc dot gnu.org
2021-12-07  9:44 ` rguenth at gcc dot gnu.org
2021-12-07 13:54 ` ppalka at gcc dot gnu.org
2021-12-07 14:08 ` ppalka at gcc dot gnu.org
2021-12-07 14:20 ` mpolacek at gcc dot gnu.org
2022-04-28 10:16 ` pinskia at gcc dot gnu.org
2022-10-16 15:42 ` pinskia 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-103593-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).