Tom Van Cutsem

Since you asked for my opinion: yes, it makes sense to make whitelisting a pay-as-you-go feature that you don't pay for if you don't need it. I also think making...

Can you elaborate on your objections? Is it the change from `convertArgumentToProxy` to `getProxy`? The options object? The fact that `from:` and `to:` can contain a symbolic name rather than...

Ok, I now understand better. If the args are all required, and there's already an options object, then this refactoring is difficult. You're probably right passing the name instead of...

I have had similar thoughts. In particular, your point about trapping the existing properties of an object on an ES5 engine without any support for proxies. The reason I haven't...

I just committed a patch so that `Array.isArray` and `Object.prototype.toString` automatically unwrap proxies. Those methods now return the expected result on proxies for arrays: ``` js var p = Proxy([]...

Not yet. Thanks for bringing it to my attention. I'll upload a new npm package shortly.

npm module v0.0.5 now contains the patches to `Array.isArray` and `Object.prototype.toString` to unwrap proxies.

I'm not sure what the best approach is to this kind of problem (not loading a polyfill if the platform already supports it). Right now the library is smart enough...

Symbols are not supported by this shim, as they are not available in ES5. Can you provide a little more info about your environment? Are you using a tool like...

I'll try to replicate and see what the behavior is. If v8's Symbol implementation is incompatible with its Proxy implementation, there is little this shim can do. But perhaps the...