public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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 3535 changes to ranges::join_view
Date: Wed, 20 Oct 2021 19:57:03 +0100	[thread overview]
Message-ID: <CACb0b4nm99Y0dmNzvWfJZaGUCb_aqU=ibf1zH9GCf5WDyR33ag@mail.gmail.com> (raw)
In-Reply-To: <20211020165942.1827062-1-ppalka@redhat.com>

On Wed, 20 Oct 2021 at 18:03, Patrick Palka via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk, and branches
> after a while?

Yes for all.


>
> libstdc++-v3/ChangeLog:
>
>         * include/std/ranges (join_view::__iter_cat::_S_iter_cat): Adjust
>         criteria for returning bidirectional_iterator_tag as per LWG3535.
>         (join_view::_Iterator::_S_iter_concept): Likewise.
> ---
>  libstdc++-v3/include/std/ranges | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/libstdc++-v3/include/std/ranges b/libstdc++-v3/include/std/ranges
> index 273699aa790..c1519c7dbd5 100644
> --- a/libstdc++-v3/include/std/ranges
> +++ b/libstdc++-v3/include/std/ranges
> @@ -2523,7 +2523,8 @@ namespace views::__adaptor
>             using _OuterCat = typename iterator_traits<_Outer_iter>::iterator_category;
>             using _InnerCat = typename iterator_traits<_Inner_iter>::iterator_category;
>             if constexpr (derived_from<_OuterCat, bidirectional_iterator_tag>
> -                         && derived_from<_InnerCat, bidirectional_iterator_tag>)
> +                         && derived_from<_InnerCat, bidirectional_iterator_tag>
> +                         && common_range<range_reference_t<_Base<_Const>>>)
>               return bidirectional_iterator_tag{};
>             else if constexpr (derived_from<_OuterCat, forward_iterator_tag>
>                                && derived_from<_InnerCat, forward_iterator_tag>)
> @@ -2575,7 +2576,8 @@ namespace views::__adaptor
>           {
>             if constexpr (_S_ref_is_glvalue
>                           && bidirectional_range<_Base>
> -                         && bidirectional_range<range_reference_t<_Base>>)
> +                         && bidirectional_range<range_reference_t<_Base>>
> +                         && common_range<range_reference_t<_Base>>)
>               return bidirectional_iterator_tag{};
>             else if constexpr (_S_ref_is_glvalue
>                                && forward_range<_Base>
> --
> 2.33.1.711.g9d530dc002
>


      reply	other threads:[~2021-10-20 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 16:59 Patrick Palka
2021-10-20 18:57 ` 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='CACb0b4nm99Y0dmNzvWfJZaGUCb_aqU=ibf1zH9GCf5WDyR33ag@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).