Rename allocateUTF8OnStack -> stringToUTF8OnStack #19092
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
Member
|
WDYT about "stringToStackUTF8" instead? |
Collaborator
Author
|
Or maybe just @juj WDYT about naming |
Collaborator
|
Looks good. I think I maybe |
juj
approved these changes
Mar 30, 2023
The old name is still available as an alias in library_legacy.js. Followup to #19089
sbc100
force-pushed
the
deprecate_allocateUTF8OnStack
branch
from
af217b3 to
33e19a6
Compare
sbc100
changed the title
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.
The old name is still available as an alias in library_legacy.js.
Followup to #19089