public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arthur.j.odwyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96213] New: GCC doesn't complain about ill-formed non-dependent template default argument Date: Thu, 16 Jul 2020 00:06:35 +0000 [thread overview] Message-ID: <bug-96213-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96213 Bug ID: 96213 Summary: GCC doesn't complain about ill-formed non-dependent template default argument Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: arthur.j.odwyer at gmail dot com Target Milestone: --- Possibly related (although these seem to complain about the opposite of what I'm complaining about): - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12672 - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58071 // https://godbolt.org/z/EYzxx9 template<class> int g; template<int = g<int>(0,1,2)> void h() { } int main() { h<1>(); } MSVC and Clang both reject template `h` as ill-formed, because `g<int>(0,1,2)` is nonsense -- `g<int>` is an `int` and thus cannot be called like a function. GCC accepts template `h` as well-formed, and in fact will treat this as a SFINAE situation: template<class> int g; template<int = g<int>(42)> void h() {} // #1 template<class = void> void h() {} // #2 int main() { h<>(); // unambiguously calls #2, because #1 has a deduction failure } My guess is that MSVC and Clang are closer to correct here.
next reply other threads:[~2020-07-16 0:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-16 0:06 arthur.j.odwyer at gmail dot com [this message] 2020-07-16 19:48 ` [Bug c++/96213] " mpolacek at gcc dot gnu.org 2020-07-23 20:27 ` arthur.j.odwyer at gmail dot com 2023-11-09 19:44 ` 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-96213-4@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).