--- Comment #3 from Kenji Hara <k.hara...@gmail.com> 2012-01-02 03:19:13 PST ---
(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
Finally, the overload should be resolved.
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------