What constitutes a sufficiently compelling use case?
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 638
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #73 and the proposal repository context around the ROI of a Decimal implementation and current BigInt usage. The issue does not name files or tests; progress would mean documenting a sufficiently compelling use case or threshold and tracking the supporting evidence here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100