-
Notifications
You must be signed in to change notification settings - Fork 145
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
Check sign flag for i{8, 16, 32, ...} conversions #1867
Merged
Merged
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
edcd6f3
Check sign flag for i{8, 16, 32, ...} conversions
jacogr 4704647
Ensure negative path is tested on i32 perf
jacogr 26dbfb4
CHANGELOG
jacogr ff9d02a
Comment check on top-most signed bit
jacogr 54b65b0
toBn test array
jacogr 26e33f0
toNumber uses exposed toBn tests
jacogr 191029f
Re-use tests in toBn
jacogr 31c1a9a
Re-use expectations inside bnToU8a
jacogr a847d66
Remove explicit BE (swap to non-optimal reverse)
jacogr a062e85
Adjust
jacogr 0654290
Remove defunct "only BE" comment
jacogr 270c10a
typo
jacogr 5f523b3
Use bnToU8a tests in biToU8a
jacogr 34e0ef7
Flatten tests
jacogr 3abc4b5
Additional tests
jacogr 2403866
Additional tests
jacogr 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
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.
So to understand this,
isNegative
will not indicate if we want to convert asigned
value, correct?If so maybe it would be good to refactor the name to
isSigned
and deprecateisNegative
option?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.
The naming
isNegative
is indeed very unfortunate, it does meanisSigned
and should have been named such 5 year ago. Got it right eventually in the api.The timelines for deprecation (at least 6 months and then in the next major) and then the additional clutches it brings code & maintenance wise to support old/new has newer seemed to be worth the effort. So it is a wart.