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++/104041] static_assert failure triggered by non-selected template specialization Date: Sat, 15 Jan 2022 09:03:51 +0000 [thread overview] Message-ID: <bug-104041-4-dYI5FhDOQv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104041-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104041 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Since the value that is done in the static_assert is not value dependent, it is rejected at the definition time of C<T>::C<T>. This is correct. Can you use either do the following instead: template <typename T> struct C { C(T) = delete; }; Which requires a specialization for C<T>::C<T> so it will not be a deleted constructor.
next prev parent reply other threads:[~2022-01-15 9:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-15 8:54 [Bug c++/104041] New: " bugzilla at cems dot de 2022-01-15 9:03 ` pinskia at gcc dot gnu.org [this message] 2022-01-15 9:19 ` [Bug c++/104041] " bugzilla at cems dot de 2022-01-15 9:20 ` pinskia at gcc dot gnu.org 2022-01-15 12:24 ` redi at gcc dot gnu.org 2023-02-18 21:19 ` 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-104041-4-dYI5FhDOQv@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).