From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Add specializations for some variable templates
Date: Thu, 1 Sep 2022 20:33:40 +0100 [thread overview]
Message-ID: <20220901193340.352562-1-jwakely@redhat.com> (raw)
Tested powerpc64le-linux, pushed to trunk.
-- >8 --
This avoids having to instantiate a class template when we can detect
the true cases easily with a partial specialization.
libstdc++-v3/ChangeLog:
* include/std/type_traits (is_lvalue_reference_v)
(is_rvalue_reference_v, is_reference_v, is_const_v)
(is_volatile_v): Define using partial specializations instead
of instantiating class templates.
---
libstdc++-v3/include/std/type_traits | 24 +++++++++++++++++-------
1 file changed, 17 insertions(+), 7 deletions(-)
diff --git a/libstdc++-v3/include/std/type_traits b/libstdc++-v3/include/std/type_traits
index 52cca8bf3af..e4b9b59ce08 100644
--- a/libstdc++-v3/include/std/type_traits
+++ b/libstdc++-v3/include/std/type_traits
@@ -3153,11 +3153,13 @@ template <typename _Tp, size_t _Num>
template <typename _Tp>
inline constexpr bool is_pointer_v = is_pointer<_Tp>::value;
template <typename _Tp>
- inline constexpr bool is_lvalue_reference_v =
- is_lvalue_reference<_Tp>::value;
+ inline constexpr bool is_lvalue_reference_v = false;
template <typename _Tp>
- inline constexpr bool is_rvalue_reference_v =
- is_rvalue_reference<_Tp>::value;
+ inline constexpr bool is_lvalue_reference_v<_Tp&> = true;
+template <typename _Tp>
+ inline constexpr bool is_rvalue_reference_v = false;
+template <typename _Tp>
+ inline constexpr bool is_rvalue_reference_v<_Tp&&> = true;
template <typename _Tp>
inline constexpr bool is_member_object_pointer_v =
is_member_object_pointer<_Tp>::value;
@@ -3173,7 +3175,11 @@ template <typename _Tp>
template <typename _Tp>
inline constexpr bool is_function_v = is_function<_Tp>::value;
template <typename _Tp>
- inline constexpr bool is_reference_v = is_reference<_Tp>::value;
+ inline constexpr bool is_reference_v = false;
+template <typename _Tp>
+ inline constexpr bool is_reference_v<_Tp&> = true;
+template <typename _Tp>
+ inline constexpr bool is_reference_v<_Tp&&> = true;
template <typename _Tp>
inline constexpr bool is_arithmetic_v = is_arithmetic<_Tp>::value;
template <typename _Tp>
@@ -3187,9 +3193,13 @@ template <typename _Tp>
template <typename _Tp>
inline constexpr bool is_member_pointer_v = is_member_pointer<_Tp>::value;
template <typename _Tp>
- inline constexpr bool is_const_v = is_const<_Tp>::value;
+ inline constexpr bool is_const_v = false;
template <typename _Tp>
- inline constexpr bool is_volatile_v = is_volatile<_Tp>::value;
+ inline constexpr bool is_const_v<const _Tp> = true;
+template <typename _Tp>
+ inline constexpr bool is_volatile_v = false;
+template <typename _Tp>
+ inline constexpr bool is_volatile_v<volatile _Tp> = true;
template <typename _Tp>
inline constexpr bool is_trivial_v = is_trivial<_Tp>::value;
template <typename _Tp>
--
2.37.2
reply other threads:[~2022-09-01 19:33 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=20220901193340.352562-1-jwakely@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).