-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
refactor(ast, transformer)!: remove BlockStatement::new
methods
#6783
refactor(ast, transformer)!: remove BlockStatement::new
methods
#6783
Conversation
Your org has enabled the Graphite merge queue for merging into mainAdd the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
BlockStatement::new
methodsBlockStatement::new
methods
@Boshen I imagine something in this stack will break Rolldown. I assume they have access to |
CodSpeed Performance ReportMerging #6783 will not alter performanceComparing Summary
|
Merge activity
|
38530e2
to
2bee4e2
Compare
First of a series of PRs removing
new
andnew_with_scope_id
etc methods from AST types. Following #6760, all AST node creation can now go via the AST builder.This lays groundwork for Node IDs (#5689), as we'll need
NodeId
s to be generated inAstBuilder
, so that all nodes receive an ID.