From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Adjust doxygen markup for variable templates group [PR101307]
Date: Fri, 16 Jul 2021 08:41:14 +0100 [thread overview]
Message-ID: <YPE4GjPQMQd6P69z@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 145 bytes --]
libstdc++-v3/ChangeLog:
PR libstdc++/101307
* include/std/type_traits: Adjust doxygen markup.
Tested powerpc64le-linux. Committed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1355 bytes --]
commit da89dfc2a0cb29d3d8a4f2394eee90d150cf6185
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Jul 15 21:13:34 2021
libstdc++: Adjust doxygen markup for variable templates group [PR101307]
libstdc++-v3/ChangeLog:
PR libstdc++/101307
* include/std/type_traits: Adjust doxygen markup.
diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits
index 91d65234f23..8d9c6394cd8 100644
--- a/libstdc++-v3/include/std/type_traits
+++ b/libstdc++-v3/include/std/type_traits
@@ -3096,17 +3096,18 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
#if __cplusplus >= 201703L
# define __cpp_lib_type_trait_variable_templates 201510L
/**
- * @defgroup variable_templates Variable templates for type traits.
+ * @defgroup variable_templates Variable templates for type traits
* @ingroup metaprogramming
*
- * The variable `is_foo_v<T>` is a boolean constant with the same value
- * as the type trait `is_foo<T>::value`.
+ * Each variable `is_xxx_v<T>` is a boolean constant with the same value
+ * as the `value` member of the corresponding type trait `is_xxx<T>`.
*
* @since C++17
*/
- /** @ingroup variable_templates
+ /**
* @{
+ * @ingroup variable_templates
*/
template <typename _Tp>
inline constexpr bool is_void_v = is_void<_Tp>::value;
reply other threads:[~2021-07-16 7:41 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=YPE4GjPQMQd6P69z@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).