> Le 10 nov. 2016 à 15:50, Isiah Meadows <[email protected]> a écrit :
>
> This could be resolved by checking the underlying non-proxy object and using
> that one's internal slots instead, in each language-level method that checks
> that.
>
Such semantics could make impossible to write impermeable proxies for some
objects, e.g.
```js
let s = new Set
let sProxy = new Proxy(s, { /* .... */ })
Set.prototype.add.call(sProxy, "foo") // will add "foo" to `s`, even if you
were careful enough to intercept `sProxy.add("foo")`
Set.prototype.has.call(sProxy, "bar") // will reveal whether "bar" is in `s`
```
—Claude_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
