-
Notifications
You must be signed in to change notification settings - Fork 26.8k
Bitshift performance vs 64bit numbers #109
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@tbcm interesting, maybe you should provide some examples for the guide |
I had found a good website about this a few weeks ago, because I ran into this issue. I cannot find it anymore, but here is a stackoverflow link: At the moment I'm very busy, so I cannot create an example. I just thought it would be good to know. |
Ah! Thanks for pointing this out. 🍻 |
🍻 thank you! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Every number is stored with 64bit, except you are doing bit shifting. Then javascript stores the number into a 32bit integer. The result of this: You get negative or just wrong numbers when you are shifting a big js-representing integer.
If you really think bit shift is a good way to improve performance, make sure the numbers are not bigger than 32 bit.
The text was updated successfully, but these errors were encountered: