public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tdb at tdb dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84920] Better handling of unmatched/ambiguous calls
Date: Tue, 16 Nov 2021 17:32:12 +0000	[thread overview]
Message-ID: <bug-84920-4-MrTY4Pqm7m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-84920-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84920

Mikko Rasa <tdb at tdb dot fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tdb at tdb dot fi

--- Comment #7 from Mikko Rasa <tdb at tdb dot fi> ---
Is this still being worked on?  I regularly run into spammy output, especially
with the == and != operators.  Just now I accidentally used std::find on an
std::map, which obviously didn't work - but spewed nearly 500 lines of notes
about all the operator== overloads it considered from several stdlib headers. 
At that point the notes cease to be useful and just make it harder to find out
where the actual error was.  This occurs with both g++-10 and g++-11.

  parent reply	other threads:[~2021-11-16 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-84920-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` jakub at gcc dot gnu.org
2021-06-01  8:10 ` rguenth at gcc dot gnu.org
2021-11-16 17:32 ` tdb at tdb dot fi [this message]
2022-01-02 11:59 ` redi at gcc dot gnu.org
2022-06-08 22:04 ` lhyatt at gcc dot gnu.org
2022-06-09 11:19 ` redi at gcc dot gnu.org
2022-06-09 13:37 ` lhyatt 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-84920-4-MrTY4Pqm7m@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: link
Be 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).