From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Document P1739R4 status [PR100139]
Date: Thu, 19 Aug 2021 15:06:06 +0100 [thread overview]
Message-ID: <YR5lTkmyVCwNNTVz@redhat.com> (raw)
In-Reply-To: <YR5IqR4ZeW3djXOu@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 512 bytes --]
On 19/08/21 13:03 +0100, Jonathan Wakely wrote:
>We should document the status of this unimplemented feature.
>
>Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
>
>libstdc++-v3/ChangeLog:
>
> PR libstdc++/100139
> * doc/xml/manual/status_cxx2020.xml: Add P1739R4 to status table.
> * doc/html/manual/status.html: Regenerate.
>
I forgot that I'd grouped all the Ranges and Concepts papers together
in the status table. This moves the new row to be in that group.
Committed to trunk and 10 and 11 branches.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1792 bytes --]
commit c5e0f954aef8caf4ee54b185e0fbfa88aeab62c6
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Aug 19 15:03:21 2021
libstdc++: Move status table entry to be with other ranges papers
Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
libstdc++-v3/ChangeLog:
* doc/xml/manual/status_cxx2020.xml: Move row earlier in table.
* doc/html/manual/status.html: Regenerate.
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
index 45de79311a1..a729ddd3ada 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
@@ -545,6 +545,16 @@ or any notes about the implementation.
<entry />
</row>
+ <row>
+ <?dbhtml bgcolor="#C8B0B0" ?>
+ <entry> Avoid template bloat for <code>safe_ranges</code> in combination with ‘subrange-y’ view adaptors.</entry>
+ <entry>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1739r4.html">
+ P1739R4 </link>
+ </entry>
+ <entry align="center"> </entry>
+ <entry />
+ </row>
<row>
@@ -1437,17 +1447,6 @@ or any notes about the implementation.
<entry />
</row>
- <row>
- <?dbhtml bgcolor="#C8B0B0" ?>
- <entry> Avoid template bloat for <code>safe_ranges</code> in combination with ‘subrange-y’ view adaptors.</entry>
- <entry>
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1739r4.html">
- P1739R4 </link>
- </entry>
- <entry align="center"> </entry>
- <entry />
- </row>
-
</tbody>
</tgroup>
</table>
prev parent reply other threads:[~2021-08-19 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 12:03 Jonathan Wakely
2021-08-19 14:06 ` Jonathan Wakely [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=YR5lTkmyVCwNNTVz@redhat.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).