public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/redhat/heads/gcc-8-branch)] libstdc++: Document correct feature test macro, __cpp_lib_is_invocable
Date: Thu, 17 Sep 2020 16:57:14 +0000 (GMT) [thread overview]
Message-ID: <20200917165714.B4C7F398E80F@sourceware.org> (raw)
https://gcc.gnu.org/g:3d65160fc0ebcac690651163534ea06596ef1b4b
commit 3d65160fc0ebcac690651163534ea06596ef1b4b
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Apr 21 17:26:52 2020 +0100
libstdc++: Document correct feature test macro, __cpp_lib_is_invocable
The std::is_callable trait was renamed to is_invocable, but I never
updated the manual to reflect the updated feature test macro.
* doc/xml/manual/status_cxx2017.xml: Fix name of feature test macro.
* doc/html/*: Regenerate.
Diff:
---
libstdc++-v3/ChangeLog | 5 +++++
libstdc++-v3/doc/html/manual/status.html | 2 +-
libstdc++-v3/doc/xml/manual/status_cxx2017.xml | 2 +-
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 495f6809729..8d3f7f9b185 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,8 @@
+2020-04-21 Jonathan Wakely <jwakely@redhat.com>
+
+ * doc/xml/manual/status_cxx2017.xml: Fix name of feature test macro.
+ * doc/html/*: Regenerate.
+
2020-04-03 Jonathan Wakely <jwakely@redhat.com>
Backport from mainline
diff --git a/libstdc++-v3/doc/html/manual/status.html b/libstdc++-v3/doc/html/manual/status.html
index 970c73d992b..189b4e5eda2 100644
--- a/libstdc++-v3/doc/html/manual/status.html
+++ b/libstdc++-v3/doc/html/manual/status.html
@@ -689,7 +689,7 @@ Feature-testing recommendations for C++</a>.
<a class="link" href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0077r2.html" target="_top">
P0077R2
</a>
- </td><td align="center"> 7.1 </td><td align="left"><code class="code"> __cpp_lib_is_callable >= 201603 </code></td></tr><tr><td align="left"> has_unique_object_representations </td><td align="left">
+ </td><td align="center"> 7.1 </td><td align="left"><code class="code"> __cpp_lib_is_invocable >= 201703 </code></td></tr><tr><td align="left"> has_unique_object_representations </td><td align="left">
<a class="link" href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0258r2.html" target="_top">
P0258R2
</a>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
index 7b5b4c41209..3931a7a71f9 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
@@ -458,7 +458,7 @@ Feature-testing recommendations for C++</link>.
</link>
</entry>
<entry align="center"> 7.1 </entry>
- <entry><code> __cpp_lib_is_callable >= 201603 </code></entry>
+ <entry><code> __cpp_lib_is_invocable >= 201703 </code></entry>
</row>
<row>
reply other threads:[~2020-09-17 16:57 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=20200917165714.B4C7F398E80F@sourceware.org \
--to=jakub@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.org \
--cc=libstdc++-cvs@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).