public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13979] Error message about no matching function for call with derived class arguments could be improved
Date: Wed, 05 Aug 2009 13:42:00 -0000 [thread overview]
Message-ID: <20090805134219.8934.qmail@sourceware.org> (raw)
In-Reply-To: <bug-13979-7764@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from jason at redhat dot com 2009-08-05 13:42 -------
Subject: Re: Error message about no matching function for
call with derived class arguments could be improved
On 08/04/2009 06:42 PM, manu at gcc dot gnu dot org wrote:
> I don't even know if we have different codepaths for those!
We do: if there's a conversion that seems likely but invalid, we build
it up but set bad_p on it so that we can give a more helpful diagnostic
when we try to use it.
Jason
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13979
next prev parent reply other threads:[~2009-08-05 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13979-7764@http.gcc.gnu.org/bugzilla/>
2009-08-04 16:02 ` manu at gcc dot gnu dot org
2009-08-04 17:48 ` jwakely dot gcc at gmail dot com
2009-08-04 22:42 ` manu at gcc dot gnu dot org
2009-08-05 10:03 ` jwakely dot gcc at gmail dot com
2009-08-05 13:42 ` jason at redhat dot com [this message]
2004-02-02 14:50 [Bug c++/13979] New: no matching function for call with derived class arguments bkramer at ciprico dot com
2004-02-15 21:59 ` [Bug c++/13979] Error message about no matching function for call with derived class arguments could be improved mmitchel at gcc dot gnu dot org
2004-08-11 22:16 ` pinskia at gcc dot gnu dot org
2005-03-21 22:17 ` bangerth at dealii dot 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=20090805134219.8934.qmail@sourceware.org \
--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).