public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "waffl3x at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/83417] Pointer-to-member template parameter with auto member type dependent container type does not work (C++17) Date: Fri, 15 Dec 2023 17:23:16 +0000 [thread overview] Message-ID: <bug-83417-4-vWswSsYDRf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-83417-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83417 waffl3x <waffl3x at protonmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |waffl3x at protonmail dot com --- Comment #5 from waffl3x <waffl3x at protonmail dot com> --- https://godbolt.org/z/Kxco7c5Es Still not working in trunk, was it ever decided on whether or not this is well-formed? ``` template<auto> struct C {}; template <typename T, typename U, U T::* V> void zoink(C<V>) { } struct S { int _m; }; void go() { zoink(C<&S::_m>{}); } ``` https://godbolt.org/z/ohG9ra5en This is the workaround I would use, it has better ergonomics anyway. I believe we should decide on whether this truly is a bug or not and if not just simply close it. Credit to Tsche for pointing this case out to me.
prev parent reply other threads:[~2023-12-15 17:23 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-83417-4@http.gcc.gnu.org/bugzilla/> 2020-10-16 16:05 ` mpolacek at gcc dot gnu.org 2021-01-27 14:36 ` davveston at gmail dot com 2021-02-03 10:01 ` davveston at gmail dot com 2023-12-15 17:23 ` waffl3x at protonmail dot com [this message]
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-83417-4-vWswSsYDRf@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).