Skip to content

Deprecate allocateUTF8 in favor of stringToNewUTF8 #19089

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

Merged
merged 1 commit into from
Mar 29, 2023
Merged

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Mar 28, 2023

Followup to #19064

@sbc100 sbc100 requested review from juj and tlively March 28, 2023 20:40
@@ -226,9 +226,9 @@ mergeInto(LibraryManager.library, {

// Allocate heap space for a JS string, and write it there.
// It is the responsibility of the caller to free() that memory.
$allocateUTF8: function(str) {
$stringToNewUTF8: function(str) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would probably be good to collect the contents of runtime_strings.js (including the accompanying stringToUTF8) here as well.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that is part of our overall goal of moving things from runtime to library functions..

@sbc100 sbc100 merged commit 4e15675 into main Mar 29, 2023
@sbc100 sbc100 deleted the deprecate_allocateUTF8 branch March 29, 2023 16:48
sbc100 added a commit that referenced this pull request Mar 29, 2023
The old name is still available as an alias in library_legacy.js.

Followup to #19089
RReverser pushed a commit that referenced this pull request Mar 29, 2023
@juj
Copy link
Collaborator

juj commented Mar 30, 2023

Thanks, looks good!

sbc100 added a commit that referenced this pull request Mar 30, 2023
The old name is still available as an alias in library_legacy.js.

Followup to #19089
sbc100 added a commit that referenced this pull request Mar 30, 2023
The old name is still available as an alias in library_legacy.js.

Followup to #19089
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants