public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107428] New: trying to define a partial specialized concept does not give a good error message Date: Wed, 26 Oct 2022 20:45:30 +0000 [thread overview] Message-ID: <bug-107428-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107428 Bug ID: 107428 Summary: trying to define a partial specialized concept does not give a good error message Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Take: ``` template<typename T, typename T1> concept same = false; template<typename T> concept same<T, T> = true; ``` GCC produces: ``` <source>:6:13: error: expected '=' before '<' token 6 | concept same<T, T> = true; | ^ ``` While clang produces: ``` <source>:6:9: error: name defined in concept definition must be an identifier concept same<T, T> = true; ^ ``` While clang is definitely better than GCC. We could do even better at sugguesting you can't do a partial specialization of a concept.
next reply other threads:[~2022-10-26 20:45 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-26 20:45 pinskia at gcc dot gnu.org [this message] 2022-10-26 21:42 ` [Bug c++/107428] " redi 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-107428-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: 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).