m.invoke() vs. m()
neal at gafter.com
Mon Dec 7 14:50:57 PST 2009
On Mon, Dec 7, 2009 at 2:46 PM, Osvaldo Doederlein <opinali at gmail.com>wrote:
> The problem of separate variable/method namespaces can be handled by making
> the conflict illegal - any given scope cannot see two methods, or variables
> of closure type, with the same signature.
Things are not that simple. What about nested scopes, or the scope of a
class/interface versus its subclasses/subinterfaces? Hiding? Shadowing?
Overloading? These all have to be worked out. I think it's worth doing,
but it's not trivial.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the closures-dev