From: Marek Polacek <polacek@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [wwwdocs] Document new C++ features in C++23
Date: Tue, 22 Jun 2021 13:21:22 -0400 [thread overview]
Message-ID: <YNIcEkqYbrkzqTuy@redhat.com> (raw)
It's time to start adding new C++ features.
Pushed.
commit e373348138d8d767067c0a79b3ddc6a70cbee3a4
Author: Marek Polacek <polacek@redhat.com>
Date: Tue Jun 22 13:19:37 2021 -0400
gcc-12/changes.html: Add if consteval
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 42ded16d..07f70b8b 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -72,7 +72,15 @@ a work-in-progress.</p>
</li>
</ul>
-<!-- <h3 id="cxx">C++</h3> -->
+<h3 id="cxx">C++</h3>
+<ul>
+ <li>Several C++23 features have been implemented:
+ <ul>
+ <li>P1938R3, <code>if consteval</code></li>
+ </ul>
+ </li>
+</ul>
+
<!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> -->
<!-- <h3 id="d">D</h3> -->
reply other threads:[~2021-06-22 17:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YNIcEkqYbrkzqTuy@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@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).