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++/101231] New: _CachedPosition::_M_get() should not return {} when range adapter does not model forward_range Date: Sun, 27 Jun 2021 08:15:51 +0000 [thread overview] Message-ID: <bug-101231-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101231 Bug ID: 101231 Summary: _CachedPosition::_M_get() should not return {} when range adapter does not model forward_range Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: hewillk at gmail dot com Target Milestone: --- After P2325, iterators such as basic_istream_view::iterator are no longer default_initializable, so _CachedPosition::_M_get() should not just return {} when the adapter does not model forward_range. #include <ranges> #include <sstream> int main() { auto words = std::istringstream{"42"}; auto is = std::ranges::istream_view<int>(words); auto r = is | std::views::filter([](auto) { return true; }); for (auto x : r); } https://godbolt.org/z/PejdYzc8j
next reply other threads:[~2021-06-27 8:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-27 8:15 hewillk at gmail dot com [this message] 2021-06-28 15:04 ` [Bug libstdc++/101231] " ppalka at gcc dot gnu.org 2021-07-16 13:47 ` cvs-commit at gcc dot gnu.org 2021-07-16 13:53 ` ppalka at gcc dot gnu.org 2022-02-11 14:04 ` cvs-commit at gcc dot gnu.org 2022-05-31 18:39 ` cvs-commit at gcc dot gnu.org 2022-05-31 18:46 ` 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-101231-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: 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).