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++/100631] ranges::elements_view:: _Sentinel is missing __distance_from() that can access _M_current of _Iterator Date: Mon, 17 May 2021 03:45:08 +0000 [thread overview] Message-ID: <bug-100631-4-zaEOtDKk5d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100631-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100631 --- Comment #1 from 康桓瑋 <hewillk at gmail dot com> --- Another issue is that in elements_view::_Sentinel in ranges#L3677: template<bool _Const2, typename _Base2 = __detail::__maybe_const_t<_Const2, _Vp>> requires sized_sentinel_for<sentinel_t<_Base>, iterator_t<_Base2>> friend constexpr range_difference_t<_Base2> operator-(const _Iterator<_Const2>& __x, const _Sentinel& __y) { return __x._M_current - __y._M_end; } the return type of the function is range_difference_t<_Base2>, but in [range.elements#sentinel], it is defined as range_difference_t<Base>: template<bool OtherConst> requires sized_sentinel_for<sentinel_t<Base>, iterator_t<maybe- const<OtherConst, V>>> friend constexpr range_difference_t<Base> operator-(const iterator<OtherConst>& x, const sentinel& y); Perhaps range_difference_t<Base> and range_difference_t<_Base2> are equivalent in this case, but I am not sure.
next prev parent reply other threads:[~2021-05-17 3:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-17 3:22 [Bug libstdc++/100631] New: " hewillk at gmail dot com 2021-05-17 3:45 ` hewillk at gmail dot com [this message] 2021-05-17 4:50 ` [Bug libstdc++/100631] " hewillk at gmail dot com 2021-05-17 10:29 ` ppalka at gcc dot gnu.org 2021-05-17 12:32 ` rs2740 at gmail dot com 2021-05-17 13:34 ` hewillk at gmail dot com 2021-05-18 4:35 ` cvs-commit at gcc dot gnu.org 2021-05-18 5:32 ` hewillk at gmail dot com 2021-05-18 13:50 ` ppalka at gcc dot gnu.org 2021-05-18 14:22 ` cvs-commit at gcc dot gnu.org 2021-06-10 18:54 ` cvs-commit at gcc dot gnu.org 2021-06-10 18:54 ` cvs-commit at gcc dot gnu.org 2021-06-10 18:57 ` cvs-commit at gcc dot gnu.org 2021-06-10 18:58 ` cvs-commit at gcc dot gnu.org 2021-06-10 18:58 ` 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-100631-4-zaEOtDKk5d@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).