Replies: 2 comments 1 reply
-
The more I see this comparison, the more I am unsure about its usefulness. I may understand that we want to make sure that our AST is valid because we are building from scratch, although I also think that every parser would follow undert this situation. We will create the AST based on our needs and those needs might be different from TS (or any other parser). Is it worth keep exploring it? For example, if we decided to create a CSS parser, we wouldn't have a decent comparison because the current state of CSS parsers is not that great (what we were doing was good quality). So my question stays: is it worth it? |
Beta Was this translation helpful? Give feedback.
-
#1977 should fix the issue with the sequence expression parsing |
Beta Was this translation helpful? Give feedback.
-
These are the differences found so far between tsc and our parser.
I will be updating the section below as I find new differences.
Differences
JS_ARRAY_HOLE
tsc creates an empty node where it started to search for an item, but found the "hole". We put it after the trivia of last token ("[" or ",").
.\test262\test\built-ins\Array\from\from-array.js
tsc
our parser
JS_SEQUENCE_EXPRESSION
tsc
our
Beta Was this translation helpful? Give feedback.
All reactions