-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
refactor(ecma/lexer): split lexer of parser #10377
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
Conversation
🦋 Changeset detectedLatest commit: 6b0e4fc The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
CodSpeed Performance ReportMerging #10377 will improve performances by 3.05%Comparing Summary
Benchmarks breakdown
|
It's surprising that these failing test cases parse correctly in the playground environment, yet were passing in our earlier test suite. For instance, the failing test case in |
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.
CI failed, but I guess it's #10378, right? Please feel free to fix CI in any direction - except removing the whole tests.
I agree that it's a problem, but I just didn't bother to think about the solution deeply.
4f625f4
to
e246e9a
Compare
The issue occurs because |
You can do
```toml
[features]
verify = ["swc_ecma_lexer/verify"]
```
from the swc_ecma_parser/Cargo.toml
… Message ID: ***@***.***>
|
e246e9a
to
4690101
Compare
Appreciate the clarification! The design pattern makes sense now. |
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.
Thanks!
We are not ensure each token is correct during parse js/ts code, so let's split
parse/lexer
into single crates and this crate can ensure lexer is correctly