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: Thu, 19 Jan 2023 01:26:41 +0000 [thread overview]
Message-ID: <bug-95968-4-NVKxkx8k0a@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|rejects-valid |
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> 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.
They are not until C++23 (See PR 107687 for the status on that).
This is just a diagnostic issue. add constevalue like this to the reduced
testcase allows the testcase to work:
auto t = [](const auto... args) consteval {return test_class(args...);};
Note the original testcase still has issues even if you add consteval to the
lambda and I suspect because std::apply still has issues ...
prev parent reply other threads:[~2023-01-19 1:26 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
2023-01-19 1:26 ` pinskia at gcc dot gnu.org [this message]
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-NVKxkx8k0a@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: link
Be 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).