vbuild.Fusion: Opportunistically store types as TypeIDs#7047
Merged
Conversation
nwt
reviewed
Jun 12, 2026
mattnibs
force-pushed
the
vbuild-fusion-typeids
branch
from
a1f1ec4 to
2fd4692
Compare
nwt
approved these changes
Jun 12, 2026
This commit changes how types are stored in vbuild Fusion vectors- If incoming TypeVectors store types using the loader pattern, avoid the expensive conversion to super.Types and using type ids instead.
mattnibs
force-pushed
the
vbuild-fusion-typeids
branch
from
2fd4692 to
553e12c
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This commit changes how types are stored in vbuild Fusion vectors. If incoming TypeVectors store types using the loader pattern, avoid the expensive conversion to super.Types and using type ids instead.