public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "headch at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109001] New: “no declaration matches” for complicated non-type template parameters Date: Fri, 03 Mar 2023 04:39:40 +0000 [thread overview] Message-ID: <bug-109001-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109001 Bug ID: 109001 Summary: “no declaration matches” for complicated non-type template parameters Product: gcc Version: 12.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- I’m reasonably certain (but not completely) that this is valid code: #include <algorithm> #include <cstddef> template<size_t x> class C { public: template<size_t y> C<std::max(x, y)> set(); }; template<size_t x> template<size_t y> C<std::max(x, y)> C<x>::set() { return {}; } however, GCC rejects it with “error: no declaration matches ‘C<std::max<long unsigned int>(x, y)> C<x>::set()’” on the out-of-body function definition. This is accepted in GCC 11.3, as well as the latest versions of Clang and MSVC on gcc.godbolt.org. Interestingly, GCC 12 also accepts the code if I change the function definition (just the definition, not the in-body declaration) to use trailing-return-type syntax: #include <algorithm> #include <cstddef> template<size_t x> class C { public: template<size_t y> C<std::max(x, y)> set(); }; template<size_t x> template<size_t y> auto C<x>::set() -> C<std::max(x, y)> { return {}; }
next reply other threads:[~2023-03-03 4:39 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-03 4:39 headch at gmail dot com [this message] 2023-03-03 14:12 ` [Bug c++/109001] " 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-109001-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).