From: Patrick Palka <ppalka@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, Patrick Palka <ppalka@redhat.com>
Subject: [pushed] libstdc++: Fix template-head of repeat_view::_Iterator [PR109111]
Date: Tue, 14 Mar 2023 19:20:05 -0400 [thread overview]
Message-ID: <20230314232005.1575584-1-ppalka@redhat.com> (raw)
Tested on x86_64-pc-linux-gnu, pushed to trunk as obvious.
-- >8 --
PR libstdc++/109111
libstdc++-v3/ChangeLog:
* include/std/ranges (repeat_view): Remove redundant parentheses
in requires-clause.
(repeat_view::_Iterator): Correct the requires-clause.
---
libstdc++-v3/include/std/ranges | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/libstdc++-v3/include/std/ranges b/libstdc++-v3/include/std/ranges
index 0725e700c47..b230ebefcf5 100644
--- a/libstdc++-v3/include/std/ranges
+++ b/libstdc++-v3/include/std/ranges
@@ -7407,8 +7407,8 @@ namespace views::__adaptor
#define __cpp_lib_ranges_repeat 202207L
template<copy_constructible _Tp, semiregular _Bound = unreachable_sentinel_t>
- requires (is_object_v<_Tp> && same_as<_Tp, remove_cv_t<_Tp>>
- && (__detail::__is_integer_like<_Bound> || same_as<_Bound, unreachable_sentinel_t>))
+ requires is_object_v<_Tp> && same_as<_Tp, remove_cv_t<_Tp>>
+ && (__detail::__is_integer_like<_Bound> || same_as<_Bound, unreachable_sentinel_t>)
class repeat_view : public view_interface<repeat_view<_Tp, _Bound>>
{
__detail::__box<_Tp> _M_value;
@@ -7472,7 +7472,8 @@ namespace views::__adaptor
repeat_view(_Tp, _Bound) -> repeat_view<_Tp, _Bound>;
template<copy_constructible _Tp, semiregular _Bound>
- requires __detail::__is_integer_like<_Bound> || same_as<_Bound, unreachable_sentinel_t>
+ requires is_object_v<_Tp> && same_as<_Tp, remove_cv_t<_Tp>>
+ && (__detail::__is_integer_like<_Bound> || same_as<_Bound, unreachable_sentinel_t>)
class repeat_view<_Tp, _Bound>::_Iterator
{
using __index_type
--
2.40.0
reply other threads:[~2023-03-14 23:20 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=20230314232005.1575584-1-ppalka@redhat.com \
--to=ppalka@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).