From: Jonathan Wakely <jwakely@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Implement LWG 3555 changes to transform/elements_view
Date: Fri, 18 Jun 2021 22:55:17 +0100 [thread overview]
Message-ID: <CACb0b4m+qjq5bJWT0zuoLXOzHCe62_N6UAKdkLbKo-a4Vf3Cyg@mail.gmail.com> (raw)
In-Reply-To: <20210618040010.1668974-1-ppalka@redhat.com>
On Fri, 18 Jun 2021 at 05:04, Patrick Palka via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> libstdc++-v3/ChangeLog:
>
> * include/std/ranges (transform_view::_Iterator::_S_iter_concept):
> Consider _Base instead of _Vp as per LWG 3555.
> (elements_view::_Iterator::_S_iter_concept): Likewise.
OK
> ---
> libstdc++-v3/include/std/ranges | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/libstdc++-v3/include/std/ranges b/libstdc++-v3/include/std/ranges
> index f93a880ff8a..bf85b1629f0 100644
> --- a/libstdc++-v3/include/std/ranges
> +++ b/libstdc++-v3/include/std/ranges
> @@ -1613,11 +1613,11 @@ namespace views::__adaptor
> static auto
> _S_iter_concept()
> {
> - if constexpr (random_access_range<_Vp>)
> + if constexpr (random_access_range<_Base>)
> return random_access_iterator_tag{};
> - else if constexpr (bidirectional_range<_Vp>)
> + else if constexpr (bidirectional_range<_Base>)
> return bidirectional_iterator_tag{};
> - else if constexpr (forward_range<_Vp>)
> + else if constexpr (forward_range<_Base>)
> return forward_iterator_tag{};
> else
> return input_iterator_tag{};
> @@ -3659,11 +3659,11 @@ namespace views::__adaptor
> static auto
> _S_iter_concept()
> {
> - if constexpr (random_access_range<_Vp>)
> + if constexpr (random_access_range<_Base>)
> return random_access_iterator_tag{};
> - else if constexpr (bidirectional_range<_Vp>)
> + else if constexpr (bidirectional_range<_Base>)
> return bidirectional_iterator_tag{};
> - else if constexpr (forward_range<_Vp>)
> + else if constexpr (forward_range<_Base>)
> return forward_iterator_tag{};
> else
> return input_iterator_tag{};
> --
> 2.32.0.93.g670b81a890
>
prev parent reply other threads:[~2021-06-18 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 4:00 Patrick Palka
2021-06-18 21:55 ` Jonathan Wakely [this message]
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=CACb0b4m+qjq5bJWT0zuoLXOzHCe62_N6UAKdkLbKo-a4Vf3Cyg@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=ppalka@redhat.com \
/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).