Update embind test to expose unique_ptr bug #21625
Closed
Conversation
This file contains 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
brendandahl
added a commit
to brendandahl/emscripten
that referenced
this pull request
Mar 27, 2024
As pointed out by emscripten-core#21625, when using unique_ptr's with primitive types the raw pointer was being passed between wasm and JS, but it was using the underlying type (e.g. char, int, etc) to convert the value. This means the pointer was truncated to a char at the boundary. Embind doesn't allow pointers or references to primitive types so it doesn't make sense to allow a unique_ptr for these types either.
brendandahl
added a commit
to brendandahl/emscripten
that referenced
this pull request
Mar 27, 2024
As pointed out by emscripten-core#21625, when using unique_ptr's with primitive types the raw pointer was being passed between wasm and JS, but it was using the underlying type (e.g. char, int, etc) to convert the value. This means the pointer was truncated to a char at the boundary. Embind doesn't allow pointers or references to primitive types so it doesn't make sense to allow a unique_ptr for these types either.
brendandahl
added a commit
that referenced
this pull request
Apr 8, 2024
As pointed out by #21625, when using unique_ptr's with primitive types the raw pointer was being passed between wasm and JS, but it was using the underlying type (e.g. char, int, etc) to convert the value. This means the pointer was truncated to a char at the boundary. Embind doesn't allow pointers or references to primitive types so it doesn't make sense to allow a unique_ptr for these types either.
impact-maker
pushed a commit
to impact-maker/emscripten
that referenced
this pull request
Apr 11, 2024
…core#21637) As pointed out by emscripten-core#21625, when using unique_ptr's with primitive types the raw pointer was being passed between wasm and JS, but it was using the underlying type (e.g. char, int, etc) to convert the value. This means the pointer was truncated to a char at the boundary. Embind doesn't allow pointers or references to primitive types so it doesn't make sense to allow a unique_ptr for these types either.
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.
No description provided.