public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugzilla at cems dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104041] New: static_assert failure triggered by non-selected template specialization Date: Sat, 15 Jan 2022 08:54:48 +0000 [thread overview] Message-ID: <bug-104041-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104041 Bug ID: 104041 Summary: static_assert failure triggered by non-selected template specialization Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: bugzilla at cems dot de Target Milestone: --- A static_assert failure can be triggered even by a template specialization that is not selected. The following code selects the specialization C<int> if allowed to compile, but compilation fails if there is a failing static_assert in the generic template C<T>, despite it not being selected. #include <iostream> template <typename T> struct C { C(T) { #ifdef DEBUG static_assert(false, "C<T> selected"); #endif std::cout << "C<T> selected"; } }; template <> struct C<int> { C(int) { std::cout << "C<int> selected"; } }; int main() { C c(1); } /* with macro DEBUG defined, compilation error with diagnostic: error: static assertion failed: C<T> selected without macro DEBUG defined, compiles and runs with output: C<int> selected */
next reply other threads:[~2022-01-15 8:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-15 8:54 bugzilla at cems dot de [this message] 2022-01-15 9:03 ` [Bug c++/104041] " pinskia at gcc dot gnu.org 2022-01-15 9:19 ` 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@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).