Not entirely true. Since we never care about the receiver in the case of a plain call, you could use `.bind(null)` which creates a function that lacks a `.prototype` but is constructible if the ori...
To avoid any potential collisions with trap methods, let's store the original handler as a unique symbol property on `handlerPlus`. After all that's what symbols were meant for :)
```js
const O...
I've only reviewed the implementation so far. Looks good overall, except I don't understand this `shouldThrow` condition.
Also a potential optimization: when adding a proxy to the `noTrappingSet...
I've only reviewed the implementation so far. Looks good overall, except I don't understand this `shouldThrow` condition.
Also a potential optimization: when adding a proxy to the `noTrappingSet...
> I have a feeling that we can prove an equivalent approach would be to store state on proxy objects only, since by definition ordinary objects can't be trapping.
It was obviously too late for m...
I thought about that but the main reason I suggested preinstalling traps is for performance reasons for engines that use a hidden class. I'm not sure how a proxy proto interacts with that, but in g...