-
-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Generator parsing #1575
Conversation
f75ed41
to
5578d59
Compare
Test262 conformance changes:
Fixed tests (214):
Broken tests (48):
|
boa/src/syntax/parser/statement/iteration/do_while_statement.rs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parser isn't my expertise, but LGTM.
Is this still ignoring the generator tests? |
@Razican The generator tests are not ignored on master at the moment so this changes nothing for the ignore list. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some small improvements and possible bug fixes. Looks great!
boa/src/syntax/parser/expression/primary/object_initializer/mod.rs
Outdated
Show resolved
Hide resolved
boa/src/syntax/parser/statement/declaration/hoistable/generator_decl/mod.rs
Show resolved
Hide resolved
e4b10e9
to
b459f1e
Compare
b459f1e
to
bee658b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Test262 conformance changes:
Fixed tests (216):
Broken tests (48):
|
I know this diff is pretty large, but a good amount is pasting early error handling and pretty trivial code. A big chunk of this is actually implementing lots of early error handling. Without that generator parsing only produces more failed tests. There are some new errors, but those are either related to #1391 or will be fixed with some more early error handling that I did not want to do here.
If it seems to much for one PR, I can split this.
This Pull Request fixes/closes #1557, #1527.
It changes the following:
eval
orarguments
IdentifierReference
parsing inPrimaryExpression
BindingIdentifier
LabelledItem
IfStatement
ExpressionStatement
MethodDefinition
parser (Note: I have removed theMethodDefinition
and moved the parsing into thePropertyDefinition
parser. This is done, because we cannot differentiate betweenPropertyName : AssignmentExpression
andMethodDefinition
, if we encounter aComputedPropertyName
, without parsing theComputedPropertyName
. The only other placeMethodDefinition
is used is in classes. I think we can live with implementing that parser two times. The other benefit is, that the parser is now way cleaner. Adjusting it for the classes use-case would make it even worse.)