[[Invoke]] and implicit method calls
Tom Van Cutsem
tomvc.be at gmail.com
Thu Sep 12 05:35:25 PDT 2013
2013/9/12 Till Schneidereit <till at tillschneidereit.net>
> I agree, anything else would be surprising. But can't we make the .invoke
> trap work for both [[Invoke]] and [[InvokeConditional]]? It would just
> always be called, and the places where [[InvokeConditional]] is used in the
> spec would treat it as though the required method exists on the receiver.
I don't understand. Could you expand? If Proxy.[[InvokeConditional]]
triggers the "invoke" trap, presumably the trap still needs to somehow
signal "the property wasn't callable"?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss