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++/101527] New: The implementation of std::common_iterator::operator== seems to be wrong Date: Tue, 20 Jul 2021 13:05:48 +0000 [thread overview] Message-ID: <bug-101527-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101527 Bug ID: 101527 Summary: The implementation of std::common_iterator::operator== seems to be wrong 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: --- Libstdc++'s implementation of common_iterator is similar to MSVC-STL, it defines operator== inside the class and declares template common_iterator class as a friend. But according to the description of [class.friend#10]: "Friendship is neither inherited nor transitive." this will cause the following valid codes to be rejected: std::common_iterator<int*, std::unreachable_sentinel_t> it1; std::common_iterator<const int*, std::unreachable_sentinel_t> it2; it1 == it2; https://godbolt.org/z/15ao981Wb
next reply other threads:[~2021-07-20 13:05 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-20 13:05 hewillk at gmail dot com [this message] 2021-07-20 23:10 ` [Bug libstdc++/101527] " hewillk at gmail dot com 2021-07-21 9:53 ` redi at gcc dot gnu.org 2021-07-21 15:17 ` hewillk at gmail dot com 2022-04-10 18:00 ` [Bug libstdc++/101527] The implementation of std::common_iterator and std::counted_iterator's operator== " hewillk at gmail dot com 2022-04-14 19:20 ` redi at gcc dot gnu.org 2022-05-06 8:30 ` jakub at gcc dot gnu.org 2023-05-08 12:22 ` rguenth at gcc dot gnu.org 2024-06-20 8:57 ` rguenth 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-101527-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).