Ingvar Stepanyan

Hehe, good luck :) I'd send a PR myself at least for the initial step of using SVG instead of PNG, but there's so little time and so much to...

> Cause at the very least that would save us the compression step. Quick note: I think we'd still want compression, but via SVGOMG / SVGO instead of Calibre. The...

> we need to add block statement Could you elaborate please? Where would it be inserted? In non-strict code the second function is meant to shadow the first one if...

As for the object literals - as far as I remember, Shift already converts both examples you provided to the same representation.

Understood. @dominiccooney Note however that replacing with another parser won't alleviate the problem, it can just increase the limit at which a fatal stack overflow occurs.

> Search for instances of raiseError in the auto-generated parser code: searchfox.org/mozilla-central/source/js/src/frontend/BinASTParser.cpp . @Yoric Quickly looking at these instances, is it safe to say that ES5 is fully supported and...

@arai-a Hmm, will block-scoped function also throw a syntax error or just silently work differently than in the original JavaScript?

Sounds good (well, at least it's not a silent breakage). I'll look into filtering out AST nodes in the encoder for now then.

Looks like at least lazy getters and setters (which are part of ES5) are also unsupported. Looking carefully for more, but it's hard to find all the cases from just...

@arai-a is there any reason not to fallback to parsing lazy methods/getters/setters as eager in Firefox until a proper implementation is added?