From: "Ed Smith-Rowland via libstdc++" <libstdc++@gcc.gnu.org>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, libstdc++] Doc changes for constexpr additions for C++20 status.
Date: Mon, 09 Sep 2019 17:25:00 -0000 [thread overview]
Message-ID: <8b1b4b90-790c-7dd1-33aa-e7c58d48a7e9@verizon.net> (raw)
In-Reply-To: <20190909094131.GU9487@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
On 9/9/19 5:41 AM, Jonathan Wakely wrote:
> On 05/09/19 15:45 -0400, Ed Smith-Rowland via libstdc++ wrote:
>> Here is a patch to the libstdc++ docs re constexpr additions. They
>> reflect the latest macro assignments AFAICT.
>>
>> Constexpr interator reqs are implemented in 9.1, the rest for 10.1.
>>
>> Ok?
>>
>> Should I bother adding the Constexpr interator requirements to the
>> gcc-9 branch docs?
>
> Yes please, it would be good to have that part in the gcc-9 docs. No
> need to regen the HTML on the branch at this time though.
>
> Thanks
Ok,
I committed the attached for gcc-9.
Ed
[-- Attachment #2: CL_2020 --]
[-- Type: text/plain, Size: 190 bytes --]
2019-09-09 Edward Smith-Rowland <3dw4rd@verizon.net>
Update docs for p858 - Constexpr iterator changes available since 9.1.
* doc/xml/manual/status_cxx2020.xml: Update p0858r0 status.
[-- Attachment #3: patch_2020 --]
[-- Type: text/plain, Size: 830 bytes --]
Index: doc/xml/manual/status_cxx2020.xml
===================================================================
--- doc/xml/manual/status_cxx2020.xml (revision 275522)
+++ doc/xml/manual/status_cxx2020.xml (working copy)
@@ -309,7 +309,6 @@
</row>
<row>
- <?dbhtml bgcolor="#C8B0B0" ?>
<entry> Constexpr iterator requirements </entry>
<entry>
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0858r0.html">
@@ -316,8 +315,9 @@
P0858R0
</link>
</entry>
- <entry align="center"> </entry>
- <entry />
+ <entry align="center"> 9.1 </entry>
+ <entry> <code>__cpp_lib_string_view >= 201803L</code>
+ and <code>__cpp_lib_array_constexpr >= 201803L</code> </entry>
</row>
<row>
prev parent reply other threads:[~2019-09-09 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 19:46 Ed Smith-Rowland via libstdc++
2019-09-09 9:41 ` Jonathan Wakely
2019-09-09 17:25 ` Ed Smith-Rowland via libstdc++ [this message]
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=8b1b4b90-790c-7dd1-33aa-e7c58d48a7e9@verizon.net \
--to=libstdc++@gcc.gnu.org \
--cc=3dw4rd@verizon.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=jwakely@redhat.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).