[Issue 7196] Unfair function address overload resolution

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=7196



--- Comment #4 from timon.gehr at gmx.ch 2012-01-02 11:47:18 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > This is strange - issue 52 is marked as fixed, so why does it still EVER pick
> > the wrong instance?
> 
> This problem is only when the caller of CallExp is AddrExp (== &foo).
> bug 51 is the problems on initializer and rhs of AssignExp.
> 
> > Where does the spec address the meaning of &foo if there's more than one
> > function called foo in scope?
> 
> In this case, CallExp can pick the original overload of foo in static.
> Therefore compiler should translate from (&foo)(arguments...) to
> foo(arguments...).
> Finally, the overload should be resolved.

If the compiler rewrites (&foo)(arguments...) to foo(arguments...), is it now
able to inline delegates that are called directly like for example {x++;}() ?

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------