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++/110774] Ambiguous partial ordering with non-dependent function parameter type Date: Sat, 22 Jul 2023 01:07:08 +0000 [thread overview] Message-ID: <bug-110774-4-sHNMCF3VaA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110774-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110774 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Actually 0 vs nullptr is the same: ``` template<typename T> struct A { typedef char* type; }; template<typename T> char* f1(T, char*); // #1 template<typename T> long* f1(T*, typename A<T>::type*); // #2 long* p1 = f1(p1, nullptr); // #3 ``` That is the above also gets ambiguous.
next prev parent reply other threads:[~2023-07-22 1:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-22 1:03 [Bug c++/110774] New: " bbi5291 at gmail dot com 2023-07-22 1:04 ` [Bug c++/110774] " pinskia at gcc dot gnu.org 2023-07-22 1:07 ` pinskia at gcc dot gnu.org [this message] 2023-07-22 1:12 ` pinskia at gcc dot gnu.org 2023-07-22 1:15 ` [Bug c++/110774] Ambiguous partial ordering with non-dependent function parameter type and nullptr pinskia at gcc dot gnu.org 2023-07-22 1:17 ` bbi5291 at gmail dot 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-110774-4-sHNMCF3VaA@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).