Remove error handling for JS_NewInt64, it's infallible#677
Merged
Conversation
saghul
force-pushed
the
jsint64-infallible
branch
from
76e05b9 to
63d420a
Compare
bnoordhuis
approved these changes
Nov 12, 2024
Contributor
bnoordhuis
left a comment
bnoordhuis
left a comment
There was a problem hiding this comment.
LGTM but you might as well s/JS_NewInt64\(ctx, /js_int64(/ everywhere now, I suppose?
Contributor
Author
|
Good point, I can do that yeah! |
Also use js_int64(v) internally.
saghul
force-pushed
the
jsint64-infallible
branch
from
63d420a to
a83bb4e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.