You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As this repo does not offer a discussion section, I'm opening this request for a discussion here. Curious if it has been considered to switch to the new javascript BigInt primitive type instead of the probably more and more outdated version of bn.js.
Surely, it's missing immediate benefits but some in the future would be
secure future seamless interoperability with adjacent libraries in the ecosystem,
moving dependency to javascript implementation instead of third party keeping bn.js supported on all future platforms
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
As this repo does not offer a discussion section, I'm opening this request for a discussion here. Curious if it has been considered to switch to the new javascript
BigInt
primitive type instead of the probably more and more outdated version ofbn.js
.Surely, it's missing immediate benefits but some in the future would be
secure future seamless interoperability with adjacent libraries in the ecosystem,
moving dependency to javascript implementation instead of third party keeping bn.js supported on all future platforms
more?
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt
Mostly looking for a state of affairs regarding
BigInt
adoption in pjs.The text was updated successfully, but these errors were encountered: