proposal-binary-ast

proposal-binary-ast copied to clipboard

Solved by W3C EXI?

3

A W3C WG was working on EXI for XML: https://www.w3.org/XML/EXI Their primer document: https://www.w3.org/TR/exi-primer Accoring to their publication, [*Canonical EXI*](https://www.w3.org/TR/exi-c14n), it's a W3C recommendation, as of 2018. The WG's charter...

ghost

What is the current status of this proposal?

13

As titled. Is there any progress on this proposal?

Becavalier

What about directives?

7

I haven't attempted to benchmark that, but in the current text source world, when parsing a function, the parser must: 1. start parsing with the current directives; 2. if the...

Yoric

[question] I have a question that Binary AST file can be translated directly to bytecode or it should be translated to standard AST and then translated to bytecode in browser?

2

zhijs

Function.prototype.toString()

12

It seems unnecessary to me that `Function.prototype.toString()` returns a useless placeholder token (like it does with native functions). For native functions it is fair enough, and the ECMAScript standard reflects...

xorgy

This is not immediate issue, but for tracking Background: * BinAST file encodes interface fields in IDL's order * Given we encode scope information, at the point of reading each...

arai-a

The binast files should benefit from using brotli as a file compression format with a binast-specific dictionary (that is part of the spec and built into the clients). Similar to...

pmeenan

Could the AST be based on a reduced subset of productions?

1

I'm reflecting back on the AST and the overzealous #37 and thinking I could probably narrow it down a bit further. JS has a *lot* of cases where there's multiple...

dead-claudia

Could the binary AST be...a bit more binary?

1

I'm revisiting this proposal a few months later, and I'm wondering: could this proposal *be* better specified in terms of raw bytes? Currently, it seems largely spec'd in terms of...

dead-claudia

Engines *heavily* optimize integers, and they do currently parse `1` and `1.0` *differently*, taking `1.0` as a hint it's likely used as a floating point number and `1` as a...

dead-claudia