From: Jonathan Wakely <jwakely@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed 3/4] libstdc++: Update C++23 status docs
Date: Mon, 16 May 2022 15:37:49 +0100 [thread overview]
Message-ID: <CACb0b4mErV=RhjihWwAkQ8pvxCMtXKefEE5x_jBeHBJr6cnHVw@mail.gmail.com> (raw)
In-Reply-To: <20220516135748.42548-3-jwakely@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 90 bytes --]
This documents the partial support for P2231 in the gcc-11 branch,
pushed to that branch.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1717 bytes --]
commit 5d418194ccb39346d2ad022c5b143fe00b2340ac
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Mon May 16 15:33:06 2022
libstdc++: Document support for constexpr optional (P2231R1)
The changes for std::variant are not on the gcc-11 branch though.
libstdc++-v3/ChangeLog:
* doc/xml/manual/status_cxx2023.xml: Update status.
* doc/html/manual/status.html: Regenerate.
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2023.xml b/libstdc++-v3/doc/xml/manual/status_cxx2023.xml
index f1244da9dc8..75f31f55aa9 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2023.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2023.xml
@@ -158,6 +158,23 @@ or any notes about the implementation.
<entry> <code>__cpp_lib_to_underlying >= 202102L</code> </entry>
</row>
+ <row>
+ <?dbhtml bgcolor="#B0B0B0" ?>
+ <entry> Missing constexpr in std::optional and std::variant </entry>
+ <entry>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2231r1.html">
+ P2231R1
+ </link>
+ </entry>
+ <entry align="center"> 11.3 (<code>optional</code> only) </entry>
+ <entry>
+ <informaltable colsep="0" rowsep="0" rowheader="norowheader" frame="none"><tgroup cols="1"><tbody>
+ <row><entry> <code>__cpp_lib_constexpr_optional >= 202106L</code> </entry></row>
+ <row><entry> <code>__cpp_lib_variant >= 202106L</code> </entry></row>
+ </tbody></tgroup></informaltable>
+ </entry>
+ </row>
+
<row>
<entry namest="c1" nameend="c4" align="left">
<emphasis role="bold">Strings and text</emphasis>
next prev parent reply other threads:[~2022-05-16 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 13:57 [committed 1/4] libstdc++: Fix status docs for <bit> support Jonathan Wakely
2022-05-16 13:57 ` [committed 2/4] libstdc++: Add C++23 status docs Jonathan Wakely
2022-05-16 13:57 ` [committed 3/4] libstdc++: Update " Jonathan Wakely
2022-05-16 14:37 ` Jonathan Wakely [this message]
2022-05-16 13:57 ` [committed 4/4] libstdc++: Fix hyperlink in docs Jonathan Wakely
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='CACb0b4mErV=RhjihWwAkQ8pvxCMtXKefEE5x_jBeHBJr6cnHVw@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).