-
-
Notifications
You must be signed in to change notification settings - Fork 504
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): generate Visit
methods in order of type definitions
#8891
Merged
graphite-app
merged 1 commit into
main
from
02-04-refactor_ast_generate_visit_methods_in_order_of_type_definitions
Feb 4, 2025
Merged
refactor(ast): generate Visit
methods in order of type definitions
#8891
graphite-app
merged 1 commit into
main
from
02-04-refactor_ast_generate_visit_methods_in_order_of_type_definitions
Feb 4, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Feb 4, 2025
This was referenced Feb 4, 2025
CodSpeed Performance ReportMerging #8891 will not alter performanceComparing Summary
|
This was referenced Feb 4, 2025
0e47f65
to
c46048a
Compare
5db9ab0
to
d0bab30
Compare
Merge activity
|
…8891) Pure refactor. Re-order the methods in generated `Visit` and `VisitMut` traits to be in same order they appear in source code. This simplifies and improves performance of the codegen considerably. Previously it walked the AST types recursively, with loads of checks "did I generate visitor for this type already?". Now it's just a single loop over the type definitions. I've double-checked that this does not result in new/missing visit methods. This change purely results in the same methods being output in a different order.
c46048a
to
bbb075d
Compare
d0bab30
to
a36bc5f
Compare
Base automatically changed from
02-04-refactor_ast_name_astbuilder_enum_builders_after_variant_name_not_type_name
to
main
February 4, 2025 22:59
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0-merge
Merge with Graphite Merge Queue
A-ast
Area - AST
A-ast-tools
Area - AST tools
C-cleanup
Category - technical debt or refactoring. Solution not expected to change behavior
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pure refactor. Re-order the methods in generated
Visit
andVisitMut
traits to be in same order they appear in source code.This simplifies and improves performance of the codegen considerably. Previously it walked the AST types recursively, with loads of checks "did I generate visitor for this type already?". Now it's just a single loop over the type definitions.
I've double-checked that this does not result in new/missing visit methods. This change purely results in the same methods being output in a different order.