public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110765] [13 regression] constraints on parameters of derived type in CRTP base Date: Fri, 21 Jul 2023 14:09:23 +0000 [thread overview] Message-ID: <bug-110765-4-J7rZN5ptzn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110765-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110765 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC| |ppalka at gcc dot gnu.org --- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> --- Thanks for the bug report. This looks like a dup of PR109751, which is an unexpected consequence of the CWG2596 resolution (which we proactively implement IIUC). A general workaround is to turn the constrained hidden friend into a template, so that its constraints don't get immediately checked upon instantiation of its enclosing class (at which point the derived class is still incomplete). template<class...> friend constexpr auto tag_invoke(custom::to_char, derived_type const a) noexcept requires(requires { { a.to_char() }; }) { return a.to_char(); } *** This bug has been marked as a duplicate of bug 109751 ***
next prev parent reply other threads:[~2023-07-21 14:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-21 11:38 [Bug c++/110765] New: " h2+bugs at fsfe dot org 2023-07-21 14:09 ` ppalka at gcc dot gnu.org [this message] 2023-07-21 16:07 ` [Bug c++/110765] " h2+bugs at fsfe dot 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-110765-4-J7rZN5ptzn@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).