From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Fix test that uses C++17 variable template in C++14
Date: Fri, 11 Nov 2022 05:30:54 +0000 [thread overview]
Message-ID: <20221111053054.563891-1-jwakely@redhat.com> (raw)
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This test fails if run with -std=gnu++14 because it should be using
is_convertible instead of is_convertible_v.
libstdc++-v3/ChangeLog:
* testsuite/experimental/propagate_const/observers/107525.cc:
Use type trait instead of C++17 variable template.
---
.../experimental/propagate_const/observers/107525.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libstdc++-v3/testsuite/experimental/propagate_const/observers/107525.cc b/libstdc++-v3/testsuite/experimental/propagate_const/observers/107525.cc
index e7ecff73c1a..37e970c3af4 100644
--- a/libstdc++-v3/testsuite/experimental/propagate_const/observers/107525.cc
+++ b/libstdc++-v3/testsuite/experimental/propagate_const/observers/107525.cc
@@ -32,10 +32,10 @@ test_const_conversion()
operator const int*() const = delete;
};
- static_assert(!std::is_convertible_v<const X, const int*>,
+ static_assert(!std::is_convertible<const X, const int*>::value,
"Cannot convert const X to const int*");
// So should not be able to convert const propagate_const<X> to const int*.
- static_assert(!std::is_convertible_v<const propagate_const<X>, const int*>,
+ static_assert(!std::is_convertible<const propagate_const<X>, const int*>::value,
"So should not be able to convert const propagate_const<X> to "
"const int* (although this is not what LFTSv3 says)");
}
--
2.38.1
reply other threads:[~2022-11-11 5:30 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=20221111053054.563891-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).