add math.sign and math.sign_bit overloads for int types #5956
+28
−1
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
gingerBill
reviewed
Nov 23, 2025
Comment on lines
+480
to
+483
| sign_int, | ||
| sign_i16, sign_i16le, sign_i16be, | ||
| sign_i32, sign_i32le, sign_i32be, | ||
| sign_i64, sign_i64le, sign_i64be, |
Member
There was a problem hiding this comment.
Move these to "end" of this list since the float ones are more likely to be hit. This is a "micro-optimization" but it'll help in the long run.
Contributor
Author
There was a problem hiding this comment.
done. If you wanted to micro-optimize further, would it make even more sense to put all the non-endian specific types first? i.e. f16, f32, f64, int, i16, i32, i64, f16le, etc.
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.