public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100687] [modules, concepts] imported concept gives different result Date: Thu, 25 Nov 2021 00:37:43 +0000 [thread overview] Message-ID: <bug-100687-4-VxSM6XDEbK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100687-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100687 Johel Ernesto Guerrero Peña <johelegp at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johelegp at gmail dot com --- Comment #1 from Johel Ernesto Guerrero Peña <johelegp at gmail dot com> --- I happened upon the same bug when changing a trait to be specialized directly through the variable template rather than a class template. In my case, I asserted through the variable template, so I can confirm that it's solely a bug with modules and not with concepts. See https://godbolt.org/z/jPT9T6ovP. mod.cpp: ```C++ export module mod; export template< class T > inline constexpr bool probe = false; // template< class R, class C > inline constexpr bool probe<R C::* > = true; struct S { int f( ); }; using mf_t = decltype( &S::f ); static_assert( probe< mf_t > ); ``` test.cpp: ```C++ import mod; struct S { int f( ); }; using mf_t = decltype( &S::f ); static_assert( probe< mf_t > ); ``` Output: ``` test.cpp:6:16: error: static assertion failed 6 | static_assert( probe< mf_t > ); | ^~~~~~~~~~~~~ ```
next prev parent reply other threads:[~2021-11-25 0:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-19 22:56 [Bug c++/100687] New: " webrown.cpp at gmail dot com 2021-11-25 0:37 ` johelegp at gmail dot com [this message] 2022-03-23 22:23 ` [Bug c++/100687] " johelegp at gmail dot com 2022-09-22 12:57 ` 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-100687-4-VxSM6XDEbK@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).