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++/105050] error: expression '<statement>' is not a constant expression Date: Wed, 07 Dec 2022 01:18:59 +0000 [thread overview] Message-ID: <bug-105050-4-Yxsvy2DKTY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105050-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105050 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I think clang still gives a better error message here though: <source>:43:15: error: static assertion expression is not an integral constant expression static_assert(test_swap()); ^~~~~~~~~~~ <source>:18:17: note: non-constexpr function '_M_swap_val' cannot be used in a constant expression this->_M_swap_val(__x); ^ <source>:38:6: note: in call to '&e1->swap(e2)' e1.swap(e2); ^ <source>:43:15: note: in call to 'test_swap()' static_assert(test_swap()); ^ <source>:4:10: note: declared here void _M_swap_val(expected&) { } ^
next prev parent reply other threads:[~2022-12-07 1:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-24 23:23 [Bug c++/105050] New: " redi at gcc dot gnu.org 2022-03-25 10:16 ` [Bug c++/105050] " redi at gcc dot gnu.org 2022-03-25 13:22 ` ppalka at gcc dot gnu.org 2022-03-25 13:31 ` redi at gcc dot gnu.org 2022-03-25 13:32 ` redi at gcc dot gnu.org 2022-03-26 14:20 ` cvs-commit at gcc dot gnu.org 2022-03-26 20:42 ` redi at gcc dot gnu.org 2022-12-07 1:18 ` pinskia at gcc dot gnu.org [this message] 2022-12-07 1:19 ` 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-105050-4-Yxsvy2DKTY@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).