public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ky4ct at arrl dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107278] fails to correctly parse template default function declarations. Date: Sun, 16 Oct 2022 15:26:44 +0000 [thread overview] Message-ID: <bug-107278-4-TaBfMYRHUw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107278-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107278 --- Comment #3 from Jonathan <ky4ct at arrl dot net> --- (In reply to Andrew Pinski from comment #1) > Iirc there was a defect report against the c++ standard here and you should > just foo instead of foo<T> kd5eax@KY4CT CLANG64 ~ $ cat test.cpp template<typename T> class foo { foo<T>(foo<T> const&) = delete; foo<T>(foo<T> const&&) = default; }; int main() { return 0; }; kd5eax@KY4CT CLANG64 ~ $ clang++ -std=c++20 test.cpp kd5eax@KY4CT CLANG64 ~ $ kd5eax@KY4CT UCRT64 ~ $ g++ -std=c++2b test.cpp test.cpp:4:22: error: expected ')' before 'const' 4 | foo<T>(foo<T> const&) = delete; | ~ ^~~~~~ | ) test.cpp:5:22: error: expected ')' before 'const' 5 | foo<T>(foo<T> const&&) = default; | ~ ^~~~~~ | ) kd5eax@KY4CT UCRT64 ~ $ g++ test.cpp kd5eax@KY4CT UCRT64 ~ $ (In reply to Andrew Pinski from comment #1) > Iirc there was a defect report against the c++ standard here and you should > just foo instead of foo<T> If that is the case, can you please link the defect report against the standard?
next prev parent reply other threads:[~2022-10-16 15:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-16 14:42 [Bug c++/107278] New: " ky4ct at arrl dot net 2022-10-16 15:16 ` [Bug c++/107278] " pinskia at gcc dot gnu.org 2022-10-16 15:24 ` ky4ct at arrl dot net 2022-10-16 15:26 ` ky4ct at arrl dot net [this message] 2022-10-16 15:27 ` pinskia at gcc dot gnu.org 2022-10-16 15:29 ` ky4ct at arrl dot net 2022-10-16 15:42 ` pinskia at gcc dot gnu.org 2022-10-16 15:44 ` pinskia at gcc dot gnu.org 2022-10-16 15:47 ` ky4ct at arrl dot net
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-107278-4-TaBfMYRHUw@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: linkBe 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).