From: Jason Merrill <jason@redhat.com>
To: Ed Smith-Rowland <3dw4rd@verizon.net>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Paolo Carlini <paolo.carlini@oracle.com>
Subject: Re: [C++17] Implement N3928 - Extending static_assert
Date: Wed, 17 Jun 2015 19:39:00 -0000 [thread overview]
Message-ID: <5581C912.6050704@redhat.com> (raw)
In-Reply-To: <5581B436.6060402@verizon.net>
On 06/17/2015 01:53 PM, Ed Smith-Rowland wrote:
> I tried the obvious: an error message with %qE and got 'false'.
> constexpr values are evaluated early on.
>
> Is there a possibility that late folding could help or is that
> completely different?
Late folding could help, but I think handling it in libcpp (by actually
stringizing the argument) would work better.
Jason
next prev parent reply other threads:[~2015-06-17 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 20:16 Ed Smith-Rowland
2015-05-04 15:28 ` Marek Polacek
2015-05-20 1:56 ` [PING] " Ed Smith-Rowland
2015-05-20 15:29 ` Jason Merrill
2015-06-15 16:07 ` Jason Merrill
2015-06-16 0:37 ` Ed Smith-Rowland
2015-06-17 14:44 ` Jason Merrill
2015-06-17 18:17 ` Ed Smith-Rowland
2015-06-17 19:39 ` Jason Merrill [this message]
2015-06-24 15:39 ` Ed Smith-Rowland
2015-08-04 16:10 ` Paolo Carlini
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=5581C912.6050704@redhat.com \
--to=jason@redhat.com \
--cc=3dw4rd@verizon.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.carlini@oracle.com \
/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).