Skip to content
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

What constitutes a sufficiently compelling use case? #73

Open
sarahghp opened this issue Feb 2, 2022 · 2 comments
Open

What constitutes a sufficiently compelling use case? #73

sarahghp opened this issue Feb 2, 2022 · 2 comments

Comments

@sarahghp
Copy link
Contributor

sarahghp commented Feb 2, 2022

Concerns about the ROI for a Decimal implementation have been mentioned, with the suggestion that the usage of BigInt does not currently rise to the level where the complexity is worthwhile. I am curious if we can define sufficient desire and then track it here.

@ljharb
Copy link
Member

ljharb commented Feb 2, 2022

I believe the reason BigInt hasn’t seen adoption is that it was designed explicitly not to interoperate with Number - iow, it’s not “the new integer”, it’s a specialized thing only for specific (rare) use cases.

If Decimal was designed to be “the new Number”, with easy interop between them, i suspect its adoption would be quite high.

@TehShrike
Copy link

If you want to do arithmetic with financial numbers, you need to use a library like financial-number, which is currently backed by BigInt.

A Decimal proposal, if it implemented a changePrecision method similar to financial-number, would eliminate the need for people to find a library to be able to work with financial numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants