-
Notifications
You must be signed in to change notification settings - Fork 14
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
JSBI BigInt in read.js #74 #78
Conversation
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.
looks good, dont really know whats going on tho, maybe get @eligrey to take a look
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.
We should be using real BigInts when supported natively and fallback to JSBI as needed. Only ever using JSBI may decrease performance noticeably.
I suggest keeping JSBI and polyfilling to bigint when it’s shipped widely. Interesting discussion here https://github.com/GoogleChromeLabs/jsbi |
It seems like we can use https://github.com/GoogleChromeLabs/babel-plugin-transform-jsbi-to-bigint to auto-transform JSBI to BigInt. I'm not sure if there is any reason preventing us from using the polyfill dynamically so that BigInt is used when supported. |
Okay, switching this to merge to a bigger JSBI feature branch |
Original PR #74 from @vincaslt