-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
[Merged by Bors] - Extract the ast to a crate #2402
Conversation
Test262 conformance changes
|
Codecov Report
@@ Coverage Diff @@
## main #2402 +/- ##
==========================================
- Coverage 38.36% 38.29% -0.08%
==========================================
Files 310 310
Lines 24272 24290 +18
==========================================
- Hits 9312 9301 -11
- Misses 14960 14989 +29
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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! Thanks :)
We can merge it as-is, but we might want to decide what to do with the #[must_use]
attributes. Do we want them in all getters? Is there a general guideline in the Rust community?
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.
Besides the comment by @Razican this looks perfect to me :)
bors r+ |
This should hopefully improve our compilation times, both from a clean build and from an incremental compilation snapshot. Next would be the parser, but it imports `Context`, so it'll require a bit more work. The number of file changes is obviously big, but almost nothing was changed, I just moved everything to another crate and readjusted the imports of the `parser` module. (Though, I did have to change some details, because there were some functions on the ast that returned `ParseError`s, and the tests had to be moved to the parser)
Pull request successfully merged into main. Build succeeded: |
This should hopefully improve our compilation times, both from a clean build and from an incremental compilation snapshot.
Next would be the parser, but it imports
Context
, so it'll require a bit more work.The number of file changes is obviously big, but almost nothing was changed, I just moved everything to another crate and readjusted the imports of the
parser
module. (Though, I did have to change some details, because there were some functions on the ast that returnedParseError
s, and the tests had to be moved to the parser)