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++/102283] Inconsistent/wrong overload resolution when using an initializer list and a defaulted template parameter Date: Wed, 15 Sep 2021 16:16:14 +0000 [thread overview] Message-ID: <bug-102283-4-RFYcEs2YRl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102283-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102283 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ppalka at gcc dot gnu.org --- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> --- Reduced testcase: struct A { }; struct B { }; void f(A&&); // #1 void f(const B&) = delete; // #2 int main() { f({}); } It seems Clang and MSVC consider the ICS for #1 to be better than that for #2, but I'm not sure why. According to http://eel.is/c++draft/over.ics.rank#3.3 the two ICSes should be incomparable since they initialize different classes, so at least according to that paragraph it appears GCC is behaving correctly here.
next prev parent reply other threads:[~2021-09-15 16:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-10 19:06 [Bug c++/102283] New: " dangelog at gmail dot com 2021-09-15 16:16 ` ppalka at gcc dot gnu.org [this message] 2021-09-15 20:29 ` [Bug c++/102283] " dangelog at gmail dot com 2021-09-16 13:40 ` ppalka at gcc dot gnu.org 2021-09-16 17:46 ` jason at gcc dot gnu.org 2021-10-01 17:30 ` dangelog at gmail dot com 2021-10-12 13:40 ` ppalka at gcc dot gnu.org 2021-10-12 13:47 ` 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-102283-4-RFYcEs2YRl@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).