Skip to content

Discussion: Switch from bn.js to new BigInt primitive? #5706

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

Closed
peetzweg opened this issue Aug 18, 2023 · 2 comments
Closed

Discussion: Switch from bn.js to new BigInt primitive? #5706

peetzweg opened this issue Aug 18, 2023 · 2 comments

Comments

@peetzweg
Copy link
Contributor

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

  • 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.

@jacogr
Copy link
Member

jacogr commented Aug 18, 2023

Eventually.

(The base utils already support BigInt as well)

@polkadot-js-bot
Copy link

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.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Aug 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants