receiver is indeed a bit of a misnomer for the apply trap. thisArg is
more sensible. I'll update the wiki page.
You probably missed it, but the role of the thisArg/receiver parameter
is described by example using the following code snippets on the direct
proxies wiki page:
proxy(...args); //
Le 02/09/2012 23:13, Brandon Benvie a écrit :
The use of the term receiver is somewhat misleading when put next to
the receiver in the get and set traps. For get and set the receiver is
always the proxy unless it's an object that has the proxy as its
[[prototype]]. For function invocation the
Hi,
In the proxy proposal, one can read the following signature for the
apply trap:
apply: function(target,receiver,args) - any
But the receiver doesn't make much sense to me. Is it just a typo or
am I missing something?
David
[1] http://wiki.ecmascript.org/doku.php?id=harmony:direct_proxies
On Sun, Sep 2, 2012 at 1:57 PM, David Bruant bruan...@gmail.com wrote:
Hi,
In the proxy proposal, one can read the following signature for the
apply trap:
apply: function(target,receiver,args) - any
But the receiver doesn't make much sense to me. Is it just a typo or
am I missing
Le 02/09/2012 20:38, Rick Waldron a écrit :
On Sun, Sep 2, 2012 at 1:57 PM, David Bruant bruan...@gmail.com
mailto:bruan...@gmail.com wrote:
Hi,
In the proxy proposal, one can read the following signature for the
apply trap:
apply: function(target,receiver,args) - any
The use of the term receiver is somewhat misleading when put next to the
receiver in the get and set traps. For get and set the receiver is always
the proxy unless it's an object that has the proxy as its [[prototype]].
For function invocation the receiver is the callsite object which is never
6 matches
Mail list logo
