public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "majerech.o at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107953] New: Greater-than operator misparsed inside a lambda expression used as a template argument Date: Fri, 02 Dec 2022 17:32:08 +0000 [thread overview] Message-ID: <bug-107953-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107953 Bug ID: 107953 Summary: Greater-than operator misparsed inside a lambda expression used as a template argument Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: majerech.o at gmail dot com Target Milestone: --- template <auto> void f() { } constexpr auto g = f<[] (int x, int y) { return x > y; }>; This produces the following diagnostic: <source>: In lambda function: <source>:5:50: error: expected ';' before '>' token 5 | constexpr auto g = f<[] (int x, int y) { return x > y; }>; | ^~ | ; <source>:5:51: error: expected primary-expression before '>' token 5 | constexpr auto g = f<[] (int x, int y) { return x > y; }>; | ^ ASM generation compiler returned: 1 <source>: In lambda function: <source>:5:50: error: expected ';' before '>' token 5 | constexpr auto g = f<[] (int x, int y) { return x > y; }>; | ^~ | ; <source>:5:51: error: expected primary-expression before '>' token 5 | constexpr auto g = f<[] (int x, int y) { return x > y; }>; | ^ Godbolt link to the above: https://godbolt.org/z/KG6d5E6ev Changing the body to return (x > y); makes the error go away as a workaround. So I speculate that the greater-than operator is misparsed as the end of the template argument list.
next reply other threads:[~2022-12-02 17:32 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-02 17:32 majerech.o at gmail dot com [this message] 2022-12-02 20:28 ` [Bug c++/107953] " pinskia at gcc dot gnu.org 2022-12-02 23:18 ` pinskia at gcc dot gnu.org 2022-12-02 23:23 ` pinskia at gcc dot gnu.org 2022-12-02 23:55 ` majerech.o 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-107953-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).