Optimize analysis backend #1062
Merged
Conversation
This file contains hidden or 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
6032a94 to
d80ea7a
Compare
d80ea7a to
0a32a44
Compare
leecannon
approved these changes
Mar 14, 2023
This was referenced Mar 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
based on top of #1057
fixes #536
I've benchmarked the total time required to generate semantic tokens for Sema.zig 20 times in a row.
./bench-new-debug./bench-new-fast./bench-new-safe./bench-new-small./bench-old-debug./bench-old-fast./bench-old-safe./bench-old-smallThe actual changes that improved performance are relatively small:
resolveTypeOfNodeare now cached so they never have to be recomputed