Proxy performance: JIT-compilation?

Mark Miller erights at gmail.com
Fri Aug 4 22:24:26 UTC 2017


On Fri, Aug 4, 2017 at 3:18 PM, Alex Vincent <ajvincent at gmail.com> wrote:

> In particular, for many permanently absent traps, the proxy can just pass
>> these through directly to the target without much analysis.
>>
>
> Your suggested changes to the ECMAScript specifications seem to focus on
> permanently absent traps... which doesn't do much good for present traps.
> For instance, new Proxy({}, Reflect), which I mentioned in my initial
> e-mail and, by the way, implements all the traps.  :-)
>

Hence the "many" qualification. It is true that the main use case for
proxies is membranes, in which case all traps are present. But even for
these, if the trap is permanently present, it need only be [[Get]]ed from
the handler once on initializing the proxy. Granted, this is much less
helpful for speeding up implementations, but it is not nothing ;).



>
> --
> "The first step in confirming there is a bug in someone else's work is
> confirming there are no bugs in your own."
> -- Alexander J. Vincent, June 30, 2001
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>


-- 
  Cheers,
  --MarkM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20170804/697d6bcb/attachment-0001.html>


More information about the es-discuss mailing list