Closed xuset closed 5 years ago
Yes, good point.
My plan would be to make BigInteger.js work sort of as a polyfill: check if the environment supports native bigints, if so, the library will be a thin wrapper over the native implementation. Otherwise, fall back to the library's current implementation.
Just leave here USER-SCRIPTS for all this browsers. And JavaScript is programming language for userscripts.
Chrome 67 already supports BigInt and there is a new JSBI polyfill for other browsers. I'm sure that BigInteger.js will get real boost from the native Chrome's implementation.
Resolved. BigInteger.js now works as a polyfill for the native BigInt.
This is a breaking change, you should update your major or minor version, instead of just updating patch version.
Could you clarify why it is a breaking change? What previously-functioning code is this change breaking?
Awesome project! I just found out that a new standard is being pushed forward for arbitrary sized integers and seems to have some partial support in chrome, firefox, and safari. I'm curious what this means for this project since it seems that this project could benefit greatly from the performance improvements.
Happy coding!