-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
embind: Use optional return type for vector and maps. #21102
Merged
brendandahl
merged 2 commits into
emscripten-core:main
from
brendandahl:tsgen-vector-map
Feb 2, 2024
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't this be a breaking change? I'm not sure what the policy for those are in Embind, but seems somewhat risky as users who already accessed values via the old signature, will have their code not compile after version upgrade. That switching C++ versions changes the signature seems even more risky.
Maybe safer to introduce the new method as
get_optional
/maybe_get
/ something like that, and keep the old one unconditionally there?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
User's wouldn't be directly calling this code. Only the JS code will be invoking this and the return values will be exactly the same as before in JS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah... but if it's only called internally by JS, I'm not sure I understand the value of duplicated implementation code? If it cleaned up
val
in favour ofoptional
, sure, but if we can't remove it, then keeping theval
path seems a bit easier?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we don't use
optional
here then we don't get improved type ofnumber | undefined
for typescript when using c++17. I'm hoping at some point we can drop c++11 support and the val code will go away.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see, that makes sense.
Can you add an explanatory comment to those modified places (something along the lines "this branch is used for generating more specific TypeScript types" or something) as I imagine someone looking at the code in the future will be also confused about seemingly duplicate functionality.
I'll approve PR now regardless, I just think a comment will be useful to avoid future confusion.