public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13590] unexpected overload resolution
Date: Tue, 06 Jan 2004 23:15:00 -0000 [thread overview]
Message-ID: <20040106231531.13584.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040106205426.13590.boris@kolpackov.net>
------- Additional Comments From boris at kolpackov dot net 2004-01-06 23:15 -------
Subject: Re: unexpected overload resolution
> That's not a good example. The using directive for A::f and B::f create
> an ambiguity, but this only needs to be detected when you try to call
> one of the functions, i.e. during overload resolution, not when the
> using directive is parsed.
Agree.
> However, you call f(int), and there is no ambiguity in this case.
Doesn't the overload resolution happens when I call f(int) ? And
according to what you just said it should be flagged as an error.
And thus, I think, it's a very good example ;-)
What I was trying to say is that when the same processes (overload
resolution) happens in similar situations (ambiguilty in class
inheritance vs ambiguilty in using directive) it would be nice if
it had the same result (consistency).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13590
next prev parent reply other threads:[~2004-01-06 23:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 20:54 [Bug c++/13590] New: " boris at kolpackov dot net
2004-01-06 21:10 ` [Bug c++/13590] " bangerth at dealii dot org
2004-01-06 21:56 ` boris at kolpackov dot net
2004-01-06 23:00 ` bangerth at dealii dot org
2004-01-06 23:15 ` boris at kolpackov dot net [this message]
2004-01-07 14:01 ` bangerth at dealii dot org
2004-01-11 1:05 ` [Bug c++/13590] [3.3/3.4 regression] Non-existing ambiguity when inhering through virtuals two identical using declarations giovannibajo at libero dot it
2004-01-11 1:13 ` pinskia at gcc dot gnu dot org
2004-03-05 14:44 ` [Bug c++/13590] [3.3/3.4/3.5 " nathan at gcc dot gnu dot org
2004-03-05 14:56 ` giovannibajo at libero dot it
2004-03-09 7:40 ` mmitchel at gcc dot gnu dot org
2004-06-10 20:10 ` jason at gcc dot gnu dot org
2004-06-10 22:19 ` [Bug c++/13590] [3.3/3.4/3.5 regression] [DR39] " pinskia at gcc dot gnu dot org
2004-06-18 23:46 ` mmitchel at gcc dot gnu dot org
2004-08-03 14:31 ` boris at kolpackov dot net
2004-08-14 7:21 ` pinskia at gcc dot gnu dot org
2004-10-19 11:37 ` [Bug c++/13590] [3.3/3.4/4.0 " pinskia at gcc dot gnu dot org
2005-08-31 19:34 ` [Bug c++/13590] " redi at gcc dot gnu dot org
2005-08-31 19:35 ` pinskia at gcc dot gnu 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=20040106231531.13584.qmail@sources.redhat.com \
--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).