public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96830] GCC does not complain template-head containing requires clause Date: Wed, 20 Jul 2022 09:54:27 +0000 [thread overview] Message-ID: <bug-96830-4-QeyRX3VG7n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96830-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96830 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2020-08-28 00:00:00 |2022-7-20 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Another examples: template<class T> requires true struct S { template<class U> friend struct S; }; S<int> s; EDG: "diff.C", line 5: error: requires-clause incompatible with class template "S" (declared at line 2) friend struct S; ^ detected during instantiation of class "S<T> [with T=int]" at line 8 1 error detected in the compilation of "diff.C". Clang: diff.C:4:3: error: requires clause differs in template redeclaration template<class U> ^ diff.C:8:8: note: in instantiation of template class 'S<int>' requested here S<int> s; ^ diff.C:1:28: note: previous template declaration is here template<class T> requires true ^ 1 error generated.
next prev parent reply other threads:[~2022-07-20 9:54 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-28 8:39 [Bug c++/96830] New: " p.hyundeok76 at gmail dot com 2020-08-28 11:13 ` [Bug c++/96830] " redi at gcc dot gnu.org 2020-08-28 11:24 ` redi at gcc dot gnu.org 2020-08-28 11:26 ` redi at gcc dot gnu.org 2022-07-20 9:54 ` redi at gcc dot gnu.org [this message] 2022-07-20 22:59 ` [Bug c++/96830] GCC does not complain about redeclaration with inconsistent " cvs-commit at gcc dot gnu.org 2022-07-21 11:17 ` cvs-commit at gcc dot gnu.org 2022-07-22 7:07 ` cvs-commit at gcc dot gnu.org 2022-10-02 6:59 ` oschonrock at gmail dot com 2022-10-02 18:43 ` redi at gcc dot gnu.org 2022-10-02 18:46 ` redi at gcc dot gnu.org 2022-10-03 13:58 ` redi at gcc dot gnu.org 2022-10-31 16:57 ` ppalka at gcc dot gnu.org 2023-03-13 20:40 ` ppalka at gcc dot gnu.org 2023-03-14 23:18 ` cvs-commit at gcc dot gnu.org 2023-03-14 23:18 ` cvs-commit at gcc dot gnu.org 2023-03-14 23:28 ` ppalka at gcc dot gnu.org 2023-04-27 23:04 ` cvs-commit 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-96830-4-QeyRX3VG7n@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).