That's a good point. I was thinking about this and it seems like we could flag the ParseNode somehow so that Reflect.parse could resugar. This sounds a bit like the old bad times in the decompiler (/me involuntarily shudders at memories of decompiling desugared destructuring let), but I suspect we'd have a much easier time with a parse tree. Having a more concrete idea of what you might want to desugar in the parser, do you think this would work?
----- Original Message ----- > On Fri 06 Sep 2013 18:32, Luke Wagner <[email protected]> writes: > > > 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 "remove" side, Reflect.parse makes it impossible to do > "desugaring" at the ParseNode level. Removing it would enable the > parser to express more things in terms of the AST, which would be useful > in new ES6 features. > > Andy > _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
