Le 02/11/2013 03:13, Allen Wirfs-Brock a écrit :
> On Nov 1, 2013, at 6:05 PM, David Bruant wrote:
>> I'm not sure about proxy returning "Proxy" as tag name. Is that a good idea? Brand feels like something that could safely transparently cross proxies.
> There is a note on in the ES6 draft on that Proxy case of O.P.toStirng that says: "This could be used an isProxy test.  Do we really want that?"  Nobody has answered that question yet?  What do you mean by "band" transmitted accross proxies.  ES6 has no general concept of brand.
lousy language, my mistake. I meant @@toStringTag.

> We could handle that case by internally doing O.p.toString.cal(this.[[target]]) for the proxy case.  Or we could just turn it into this.toString().  But neither of those seem particularly correct, in general.
>
> Or we could simply not special case Proxy exotic objects and then Proxies would be handled like any other object, the value of the objects @@toStringTag property would be accessed and used to compose the toString result.
Or what about a third optional argument to the Proxy constructor to set 
the @@toStringTag?

David

Le 02/11/2013 03:13, Allen Wirfs-Brock a écrit :
> On Nov 1, 2013, at 6:05 PM, David Bruant wrote:
>> I'm not sure about proxy returning "Proxy" as tag name. Is that a good idea? Brand feels like something that could safely transparently cross proxies.
>
> There is a note on in the ES6 draft on that Proxy case of O.P.toStirng that says: "This could be used an isProxy test.  Do we really want that?"  Nobody has answered that question yet?  What do you mean by "band" transmitted accross proxies.  ES6 has no general concept of brand.

lousy language, my mistake. I meant @@toStringTag.

> We could handle that case by internally doing O.p.toString.cal(this.[[target]]) for the proxy case.  Or we could just turn it into this.toString().  But neither of those seem particularly correct, in general.
>
> Or we could simply not special case Proxy exotic objects and then Proxies would be handled like any other object, the value of the objects @@toStringTag property would be accessed and used to compose the toString result.

Or what about a third optional argument to the Proxy constructor to set 
the @@toStringTag?