public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bence.kodaj at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95986] New: Partial specialization of class template is not found when class template has NTTP of class type Date: Mon, 29 Jun 2020 20:02:29 +0000 [thread overview] Message-ID: <bug-95986-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95986 Bug ID: 95986 Summary: Partial specialization of class template is not found when class template has NTTP of class type Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: bence.kodaj at gmail dot com Target Milestone: --- In the code below I would expect the static assertion __not__ to fail, but it does. OS: Ubuntu 18.04. Godbolt: https://godbolt.org/z/absUyx --------------------------- #include <type_traits> template< typename, template< auto... > typename > struct IsInstantationOf : std::false_type {}; template< template< auto... > typename Template, auto... Arg > struct IsInstantationOf< Template< Arg... >, Template > : std::true_type {}; template< std::size_t N > struct StrLiteral { constexpr StrLiteral( const char ( & )[ N ] ) {} }; template< StrLiteral > struct Template {}; int main() { const auto a = StrLiteral( "a" ); static_assert( IsInstantationOf< Template< a >, Template >::value ); return 0; } ---------------------------
next reply other threads:[~2020-06-29 20:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 20:02 bence.kodaj at gmail dot com [this message] 2021-07-20 7:46 ` [Bug c++/95986] " bence.kodaj at gmail dot com 2022-04-19 17:15 ` bence.kodaj at gmail dot com 2022-05-11 16:33 ` ppalka at gcc dot gnu.org 2022-05-11 16:48 ` bence.kodaj at gmail dot com 2022-05-11 16:55 ` ppalka 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-95986-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).