Le 06/09/2013 18:32, Luke Wagner a écrit :
This brings up a related question: what is the proposed future of the builtin
Reflect.parse now that we have pure-JS alternatives like Esprima?
On the 'keep' side, I've found jsreflect to be simple, well-written, and easy
to maintain. Also, there seem to be a existing uses of Reflect.parse from
devtools which could potentially benefit from the native performance (but I'm
not sure how it is used).
Esprima might not want to support Firefox-specific syntax (granted,
which there is less and less and hopefully which will fully disappear
eventually). But Mozilla may contribute a patch with a parsing option
for its specific syntax.
How much better is Reflect.parse performance?
I'm also happy that there exists 2 implementations as it forces
independent people/teams to agree on what is best (exactly what is
happening in this thread) instead of just shipping something
unilaterally (regardless of how well-intended).
David
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
