public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98231] New: [11 Regression] bogus error: no match for ‘operator<<’ Date: Fri, 11 Dec 2020 02:30:55 +0000 [thread overview] Message-ID: <bug-98231-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98231 Bug ID: 98231 Summary: [11 Regression] bogus error: no match for ‘operator<<’ Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mpolacek at gcc dot gnu.org Target Milestone: --- template <typename, typename = int> struct basic_ostream {}; namespace N { template <typename Char, typename CharTraits, typename T> void operator<<(basic_ostream<Char, CharTraits>, T); } basic_ostream<char> os; template<typename T> void foo (T value) { using N::operator<<; os << value; } void bar() { foo (1); } gives $ ./cc1plus -quiet ceph.C ceph.C: In instantiation of ‘void foo(T) [with T = int]’: ceph.C:14:20: required from here ceph.C:12:6: error: no match for ‘operator<<’ (operand types are ‘basic_ostream<char>’ and ‘int’) 12 | os << value; | ~~~^~~~~~~~ Started with r11-4690.
next reply other threads:[~2020-12-11 2:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-11 2:30 mpolacek at gcc dot gnu.org [this message] 2020-12-11 2:31 ` [Bug c++/98231] " mpolacek at gcc dot gnu.org 2021-01-13 16:08 ` mpolacek at gcc dot gnu.org 2021-01-13 17:00 ` mpolacek at gcc dot gnu.org 2021-01-13 22:16 ` cvs-commit at gcc dot gnu.org 2021-01-13 22:17 ` mpolacek 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-98231-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).