public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/106798] New: adjacent_view::_Iterator(_Iterator<!_Const>) requires random_access_iterator
Date: Thu, 01 Sep 2022 05:57:31 +0000	[thread overview]
Message-ID: <bug-106798-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106798

            Bug ID: 106798
           Summary: adjacent_view::_Iterator(_Iterator<!_Const>) requires
                    random_access_iterator
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hewillk at gmail dot com
  Target Milestone: ---

ranges#L5216:

    constexpr
    _Iterator(_Iterator<!_Const> __i)
      requires _Const && convertible_to<iterator_t<_Vp>, iterator_t<_Base>>
    {
      for (size_t __j = 0; __j < _Nm; ++__j)
        _M_current[__j] = std::move(__i[__j]);
    }

__i[__j] requires random_access_iterator, which is unnecessary.
ranges::move(__i._M_current, _M_current.begin()) should be enough (which
requires an extra include header).
The testcase would be


    #include <ranges>
    int main() {
      const auto r = std::views::single(0)
                   | std::views::lazy_split(0)
                   | std::views::pairwise;
      decltype(r.end()) e = auto(r).end();
    }

             reply	other threads:[~2022-09-01  5:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  5:57 hewillk at gmail dot com [this message]
2022-09-01 10:07 ` [Bug libstdc++/106798] " hewillk at gmail dot com
2022-09-01 14:04 ` ppalka at gcc dot gnu.org
2022-09-09 19:05 ` cvs-commit at gcc dot gnu.org
2022-09-09 19:06 ` ppalka at gcc dot gnu.org

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=bug-106798-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).