public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "skaniskin at berkeley dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99692] New: Lookup for operator<< skips global scope Date: Sun, 21 Mar 2021 04:01:45 +0000 [thread overview] Message-ID: <bug-99692-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99692 Bug ID: 99692 Summary: Lookup for operator<< skips global scope Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: skaniskin at berkeley dot edu Target Milestone: --- The following code is rejected by g++. #include <ostream> #include <vector> struct CustomStream : std::ostream {}; std::ostream& operator<<(std::ostream& s, const std::vector<int>&) { return s; } CustomStream&& operator<<(CustomStream&& s, const std::vector<int>& v) { static_cast<std::ostream&>(s) << v; return std::move(s); } int main() { CustomStream() << std::vector<int>{}; } The problem is there with all recent versions of gcc and independent of compiler flags
next reply other threads:[~2021-03-21 4:01 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-21 4:01 skaniskin at berkeley dot edu [this message] 2021-03-21 5:26 ` [Bug libstdc++/99692] " pinskia at gcc dot gnu.org 2021-03-21 5:28 ` pinskia at gcc dot gnu.org 2021-03-21 6:01 ` skaniskin at gmail dot com 2021-03-21 12:21 ` redi at gcc dot gnu.org 2021-03-21 12:23 ` redi at gcc dot gnu.org 2021-03-21 13:56 ` skaniskin at gmail dot com 2021-03-21 23:24 ` redi at gcc dot gnu.org 2021-05-06 4:07 ` [Bug c++/99692] " skaniskin at gmail dot com 2021-05-06 9:05 ` redi at gcc dot gnu.org 2021-05-06 9:38 ` redi at gcc dot gnu.org 2021-05-06 12:12 ` redi at gcc dot gnu.org 2021-05-06 13:07 ` redi at gcc dot gnu.org 2021-12-16 18:47 ` 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-99692-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).