public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jwjagersma at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107439] New: use of static member function in requires-expression depends on declaration order Date: Thu, 27 Oct 2022 16:22:19 +0000 [thread overview] Message-ID: <bug-107439-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107439 Bug ID: 107439 Summary: use of static member function in requires-expression depends on declaration order Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jwjagersma at gmail dot com Target Milestone: --- The following example fails to compile, as g++ complains that a declaration of 'check' is not available. Reordering it so that 'check' is declared before its use in the requires-expression makes it work. This seems inconsistent, as member functions are normally expected to be usable anywhere within the class definition. $ cat requires-memfn.cpp struct A { template<typename T> requires (check<T>()) auto func(T) { } template<typename T> static consteval bool check() { return true; } }; $ g++ -std=c++20 requires-memfn.cpp requires-memfn.cpp:3:34: error: there are no arguments to ‘check’ that depend on a template parameter, so a declaration of ‘check’ must be available [-fpermissive] 3 | template<typename T> requires (check<T>()) | ^~~~~~~~ requires-memfn.cpp:3:34: note: (if you use ‘-fpermissive’, G++ will accept your code, but allowing the use of an undeclared name is deprecated)
next reply other threads:[~2022-10-27 16:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 16:22 jwjagersma at gmail dot com [this message] 2022-10-28 14:01 ` [Bug c++/107439] " ppalka at gcc dot gnu.org 2022-10-28 14:27 ` 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-107439-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).