public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/40793] "Error: no matching function for call to XYZ" doesn't display function-template-arguments
Date: Wed, 01 Dec 2010 00:14:00 -0000	[thread overview]
Message-ID: <bug-40793-4-sXuEYWucku@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40793-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40793

--- Comment #10 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2010-12-01 00:13:52 UTC ---
(In reply to comment #9)
> So with the example in comment #5, we get:
> t.cc: In function ‘void f()’:
> t.cc:5:31: error: no matching function for call to ‘staticPrint()’
> t.cc:2:18: note: candidate is: template<class T, T t> void staticPrint()
> 
> --- CUT ---
> Is that good enough?

I don't think so. The problem is that looking at the error, one cannot say what
are the template arguments (which may be the result of something else). The
desired output is mentioned in comment #5.

Printing the candidates is of course an improvement.


  parent reply	other threads:[~2010-12-01  0:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40793-4@http.gcc.gnu.org/bugzilla/>
2010-11-30 23:59 ` pinskia at gcc dot gnu.org
2010-12-01  0:14 ` manu at gcc dot gnu.org [this message]
2011-03-23 16:46 ` jonathan.sd24 at yahoo dot de
2011-03-23 17:40 ` manu at gcc dot gnu.org
2011-09-29 10:56 ` paolo.carlini at oracle dot com
2011-09-29 10:59 ` paolo.carlini at oracle dot com
2011-09-29 12:17 ` manu at gcc dot gnu.org
2011-09-29 12:28 ` paolo.carlini at oracle dot com
2011-09-29 14:53 ` manu at gcc dot gnu.org
2011-09-29 15:12 ` paolo.carlini at oracle dot com
2009-07-17 22:09 [Bug c++/40793] New: " jonathan dot sd24 at yahoo dot de
2009-07-18  8:59 ` [Bug c++/40793] " rguenth at gcc dot gnu dot org
2009-07-18 10:02 ` jonathan dot sd24 at yahoo dot de
2009-07-21 17:46 ` jwakely dot gcc at gmail dot com
2009-07-29 21:05 ` jonathan dot sd24 at yahoo dot de
2009-08-25 14:25 ` bangerth at gmail dot com
2010-07-01  8:58 ` m-matti-a dot lehtonen at iki dot fi
2010-07-01 21:31 ` manu at gcc dot gnu dot org
2010-07-01 21:38 ` bangerth at gmail dot com

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-40793-4-sXuEYWucku@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).