public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110348] [C++26] P2741R3 - User-generated static_assert messages
Date: Tue, 12 Sep 2023 15:20:41 +0000	[thread overview]
Message-ID: <bug-110348-4-6u8SSzADRJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110348-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110348

--- Comment #13 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #12)
> BTW, shall size() and data() be manifestly constant-evaluated?
> I think it doesn't satisfy any of the https://eel.is/c++draft/expr.const#19
> bullets (unlike first static_assert argument).

Good point, I think we're missing some wording to make that all manifestly
constant-evaluated; it absolutely should be.

(In reply to Jakub Jelinek from comment #10)
> Then it should be a warning rather than error IMHO.  Because it isn't
> invalid, just likely unintended.

Agreed.

  parent reply	other threads:[~2023-09-12 15:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 16:25 [Bug c++/110348] New: " mpolacek at gcc dot gnu.org
2023-06-21 22:47 ` [Bug c++/110348] " pinskia at gcc dot gnu.org
2023-08-23 16:46 ` jakub at gcc dot gnu.org
2023-08-23 20:23 ` jakub at gcc dot gnu.org
2023-08-24 11:22 ` jakub at gcc dot gnu.org
2023-08-24 11:56 ` redi at gcc dot gnu.org
2023-08-24 12:10 ` redi at gcc dot gnu.org
2023-08-24 12:19 ` redi at gcc dot gnu.org
2023-08-24 12:28 ` jakub at gcc dot gnu.org
2023-09-12 11:30 ` corentinjabot at gmail dot com
2023-09-12 12:03 ` jakub at gcc dot gnu.org
2023-09-12 12:23 ` jakub at gcc dot gnu.org
2023-09-12 13:14 ` jakub at gcc dot gnu.org
2023-09-12 15:20 ` jason at gcc dot gnu.org [this message]
2023-09-12 15:21 ` jason at gcc dot gnu.org
2023-11-23  8:27 ` cvs-commit at gcc dot gnu.org
2023-11-23  8:42 ` jakub at gcc dot gnu.org
2023-11-23  9:38 ` corentinjabot at gmail dot com
2023-11-23  9:58 ` jakub 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-110348-4-6u8SSzADRJ@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).