public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/116011] Template declaration matching does not differentiate between &(T::x) and &T::x; only the latter can form a pointer to member Date: Sat, 20 Jul 2024 18:57:34 +0000 [thread overview] Message-ID: <bug-116011-4-cfhSwZftjT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-116011-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116011 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- It is not just templates though. It is unevulated context where the issue comes into play.
next prev parent reply other threads:[~2024-07-20 18:57 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-20 5:21 [Bug c++/116011] New: Bogus template redefinition error between pointer-to-member &T::x versus pointer &(T::x) hstong at ca dot ibm.com 2024-07-20 5:26 ` [Bug c++/116011] " pinskia at gcc dot gnu.org 2024-07-20 5:35 ` hstong at ca dot ibm.com 2024-07-20 5:44 ` pinskia at gcc dot gnu.org 2024-07-20 5:56 ` [Bug c++/116011] accepting &(T::x) as a pointer to member in an unevulated context and not treating it differently from &T::x hstong at ca dot ibm.com 2024-07-20 18:54 ` [Bug c++/116011] Template declaration matching does not differentiate between &(T::x) and &T::x; only the latter can form a pointer to member hstong at ca dot ibm.com 2024-07-20 18:57 ` pinskia at gcc dot gnu.org [this message] 2024-07-20 19:01 ` [Bug c++/116011] accepting &(T::x) as a pointer to member in an unevulated context and not treating it differently from &T::x pinskia at gcc dot gnu.org 2024-07-20 19:39 ` hstong at ca dot ibm.com 2024-07-20 19:44 ` pinskia at gcc dot gnu.org 2024-07-20 19:57 ` hstong at ca dot ibm.com
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-116011-4-cfhSwZftjT@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).