Prune nameString to reduce runtime size of Name
#1806
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
allevato
approved these changes
Jun 30, 2025
Now that the bytecode is used for generation, all entries that end up calling here will be using the raw buffer anyways, so skip trying to use the cached string.
Shrinks up the memory usage of the runtime.
thomasvl
force-pushed
the
prune_NameString
branch
from
7c4d263 to
9179770
Compare
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.
Now that the bytecode is used for messages,
descriptionalways has to construct a temporaryStringso we can just lean into that and shrink the size ofNameby removing the second property completely.