public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Tamar Christina <tnfchris@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/ARM/heads/arm-perf-staging)] libstdc++: decay in viewable_range should be remove_cvref (LWG 3375) Date: Fri, 17 Jul 2020 12:51:23 +0000 (GMT) [thread overview] Message-ID: <20200717125123.73061398C03F@sourceware.org> (raw) https://gcc.gnu.org/g:26eae9ac2bf75a26a419dc1e47a067c66331fb74 commit 26eae9ac2bf75a26a419dc1e47a067c66331fb74 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Feb 6 11:30:30 2020 +0000 libstdc++: decay in viewable_range should be remove_cvref (LWG 3375) * include/bits/stl_algobase.h (__iter_swap, __iter_swap<true>): Remove redundant _GLIBCXX20_CONSTEXPR. Diff: --- libstdc++-v3/ChangeLog | 3 +++ libstdc++-v3/include/std/ranges | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 50c4dd9b84c..a9c96ac9185 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -3,6 +3,9 @@ * include/bits/stl_algobase.h (__iter_swap, __iter_swap<true>): Remove redundant _GLIBCXX20_CONSTEXPR. + * include/std/ranges (viewable_range): Replace decay_t with + remove_cvref_t (LWG 3375). + 2020-02-05 Jonathan Wakely <jwakely@redhat.com> * include/bits/iterator_concepts.h (iter_reference_t) diff --git a/libstdc++-v3/include/std/ranges b/libstdc++-v3/include/std/ranges index ea558c76c9d..860f7283be5 100644 --- a/libstdc++-v3/include/std/ranges +++ b/libstdc++-v3/include/std/ranges @@ -92,7 +92,7 @@ namespace ranges /// A range which can be safely converted to a view. template<typename _Tp> concept viewable_range = range<_Tp> - && (safe_range<_Tp> || view<decay_t<_Tp>>); + && (safe_range<_Tp> || view<remove_cvref_t<_Tp>>); namespace __detail {
reply other threads:[~2020-07-17 12:51 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=20200717125123.73061398C03F@sourceware.org \ --to=tnfchris@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: linkBe 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).