proposal-binary-ast
proposal-binary-ast copied to clipboard
tc39
Binary AST proposal for ECMAScript
The current text of the proposal does not mention anything about mapping binary AST offsets back to source positions. If the original input is JavaScript source code, then I understand...
README states: > Why not use WebAssembly? > > There are massive existing untyped codebases, and there is no easy way to convert an untyped, garbage collected language to WebAssembly....
It is unclear to me from the documentation provided whether the size savings specified are the result of the format essentially requiring compression as part of its specification, vs actually...
For the moment, we have discussed the following annotations: - has direct eval; - let-bindings; - var-bindings; - captured names; - directives.
As @sebmarkbage and others have pointed out, the deferred-until-invocation-of-function error model is not amenable to streaming interpreters. That model is amenable to streaming compilers, but to be able to interpret...
TL;DR - this is cool because it unifies the JS ecosystem AST, and can lead to perf when compiling JS in the current toolchain. > We expect the format to...
Even if it's well-typed, Babylon ASTs permit things which are not valid JavaScript syntax (for example, module declarations in scripts). What's the idea for how to validate these ASTs? I...
> The time required to create a full AST (without verifying annotations) was reduced by ~70-90%, which is a considerable reduction since parsing time in SpiderMonkey for the plain JavaScript...
This might be beyond the scope of the current proposal, but I expect that we'll want to apply binary parsing also for JSON data. For the specific case of JSON,...
I really think this proposal is great, and I wanted to suggest the addition of one relatively small high-level goal that I didn't see in the proposal. It can be...
