public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ted at lyncon dot se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114504] New: Non-structural type accepted as non-type template parameter type Date: Wed, 27 Mar 2024 23:06:37 +0000 [thread overview] Message-ID: <bug-114504-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114504 Bug ID: 114504 Summary: Non-structural type accepted as non-type template parameter type Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ted at lyncon dot se Target Milestone: --- gcc accepts `NonStructuralType` as a non-type template parameter type below: ``` struct StructuralType1 { constexpr StructuralType1(int A) : a(A) {} int a; }; struct NonStructuralType { constexpr NonStructuralType(int A) : a(A) {} private: int a; }; template <typename T> concept is_structural = requires { []<T t> {}; }; static_assert(is_structural<StructuralType1>, "BUG! StructuralType1 is not structural"); static_assert(!is_structural<NonStructuralType>, "BUG! NontStructuralType is structural"); int main() {} ``` I was expecting `[]<T t>{}` to fail in the concept. The program compiles with clang++, icx and MSVC.
next reply other threads:[~2024-03-27 23:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-27 23:06 ted at lyncon dot se [this message] 2024-03-27 23:14 ` [Bug c++/114504] " pinskia at gcc dot gnu.org 2024-03-27 23:23 ` [Bug c++/114504] Non-structural type accepted as non-type template parameter type for a template lambda function while in a concept 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-114504-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).