public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95968] error: 'args#0' is not a constant expression Date: Mon, 17 Jan 2022 10:52:32 +0000 [thread overview] Message-ID: <bug-95968-4-AYspqlAWfb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95968-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95968 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Blocks| |55004, 54367 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The following is the reduced testcase: struct test_class { consteval test_class( double pack_) { } }; void test_func() { auto t = [](const auto... args) {return test_class(args...);}; t(1.0); } are lambdas consteval by default? I know they are implicit constexpr but I don't think they are consteval though. There is still a diagnostic issue where args#0 is used as it should be args... instead and maybe a little more clear why args... is not a constant value expression. Clang gives: <source>:8:45: error: call to consteval function 'test_class::test_class' is not a constant expression auto t = [](const auto... args) {return test_class(args...);}; ^ <source>:9:6: note: in instantiation of function template specialization 'test_func()::(anonymous class)::operator()<double>' requested here t(1.0); ^ <source>:8:56: note: function parameter 'args' with unknown value cannot be used in a constant expression auto t = [](const auto... args) {return test_class(args...);}; ^ <source>:8:31: note: declared here auto t = [](const auto... args) {return test_class(args...);}; ^ Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367 [Bug 54367] [meta-bug] lambda expressions https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004 [Bug 55004] [meta-bug] constexpr issues
next prev parent reply other threads:[~2022-01-17 10:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 15:39 [Bug c++/95968] New: " zakeria433 at gmail dot com 2020-07-08 22:45 ` [Bug c++/95968] " mpolacek at gcc dot gnu.org 2021-10-02 6:05 ` pinskia at gcc dot gnu.org 2022-01-17 10:52 ` pinskia at gcc dot gnu.org [this message] 2023-01-19 1:26 ` pinskia 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-95968-4-AYspqlAWfb@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).