-
Notifications
You must be signed in to change notification settings - Fork 27
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
bug: Inconsistent sign flag for SignedInteger64 when the result is 0 in module SignedInteger64 #147
Comments
Maybe this is also a bug for MoveStdlib, please check it when fixing this. |
pause125
added a commit
to pause125/starcoin-framework
that referenced
this issue
Oct 30, 2022
The module SignedInteger64 has nothing to do with MoveStdlib. |
7 tasks
pause125
added a commit
to pause125/starcoin-framework
that referenced
this issue
Oct 31, 2022
jolestar
pushed a commit
that referenced
this issue
Oct 31, 2022
* resolve #147 * remove unnecessary conversions
nkysg
pushed a commit
that referenced
this issue
Mar 3, 2023
* resolve #147 * remove unnecessary conversions
sanlee42
pushed a commit
that referenced
this issue
Mar 16, 2023
* resolve #147 * remove unnecessary conversions
sanlee42
pushed a commit
that referenced
this issue
Mar 22, 2023
* resolve #147 * remove unnecessary conversions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the return value of add_u64 and sub_u64 is 0, it may have a different sign flag. For example:
The text was updated successfully, but these errors were encountered: