proxy-polyfill

Proxy polyfill: assuming you are referring to this [0], since I haven't seen anything else like this, then I'll paste here what the readme says: > The polyfill supports just a limited number of proxy 'traps'. It also works by calling seal on the object passed to Proxy. This means that the properties you want to proxy must be known at creation time. i.e. that's not a polyfill for Proxy. It's a polyfill for a subset of the thing, maybe that's useful for somebody, but it's useless for the use cases I had for Proxy so far. Shipping an entire regex engine with your app: right, that's the only way to do something like that. Not that that's actually the same thing though, I can't just load this and use lookarounds as normal, i.e. it's not a polyfill. For all practical purposes these features are not polyfillable. If your idea of a polyfill inclu

1. You should probably add that link to your read me: The implementation uses `Symbol` and [`Proxy`](https://github.com/GoogleChrome/proxy-polyfill) behind the hood so you might need to use apropriate polyfills in case you want to support older browsers. 2. Personally, I find the name Nothing a bit too long. Why not use a shorter name like None?

Wrapping you code into a try/catch block decreases performance even more, you don't want to do that. You might want to check it out: https://github.com/GoogleChrome/proxy-polyfill

I've seen this one: https://github.com/GoogleChrome/proxy-polyfill

on the beginning I used getters/setters but I switched to Proxy because it allowed for simpler implementation and more flexibility. I may consider to switch back into getters/setters, if support of Proxy is really a problem (although getters/setters have its limitations). There is also Proxy polyfill, although it has the same limitations getters/setters have ("properties you want to proxy must be known at creation time"): https://github.com/GoogleChrome/proxy-polyfill