-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
⚡️ Faster rewrite of double
#5618
base: main
Are you sure you want to change the base?
Conversation
**Description** <!-- Please provide a short description and potentially linked issues justifying the need for this PR --> When we first came up with the `double` arbitrary, `bigint` were not mature enough in JavaScript. As such, we did not want our users to be forced to bump to the very last versions of Node and polyfilled it with out own 64bits bigint implementation. While it worked well and in an efficient way, it requires extra code and is probably less efficient (after further optimizations) than a native `bigint`. As such this PR drops it in favor of a `bigint`-based internal. What changes for the user? Well generated values, the shrinker. And for users blocked on legacy releases of Node (<10.5 or 10.4?), they might just not be able to use this major version of fast-check. <!-- * Your PR is fixing a bug or regression? Check for existing issues related to this bug and link them --> <!-- * Your PR is adding a new feature? Make sure there is a related issue or discussion attached to it --> <!-- You can provide any additional context to help into understanding what's this PR is attempting to solve: reproduction of a bug, code snippets... --> **Checklist** — _Don't delete this checklist and make sure you do the following before opening the PR_ - [x] The name of my PR follows [gitmoji](https://gitmoji.dev/) specification - [x] My PR references one of several related issues (if any) - [x] New features or breaking changes must come with an associated Issue or Discussion - [x] My PR does not add any new dependency without an associated Issue or Discussion - [x] My PR includes bumps details, please run `yarn bump` and flag the impacts properly - [x] My PR adds relevant tests and they would have failed without my PR (when applicable) <!-- More about contributing at https://github.com/dubzzz/fast-check/blob/main/CONTRIBUTING.md --> **Advanced** <!-- How to fill the advanced section is detailed below! --> - [x] Category: ⚡️ Improve performance - [x] Impacts: Generated values, shrinker, minimal requirements for Node <!-- [Category] Please use one of the categories below, it will help us into better understanding the urgency of the PR --> <!-- * ✨ Introduce new features --> <!-- * 📝 Add or update documentation --> <!-- * ✅ Add or update tests --> <!-- * 🐛 Fix a bug --> <!-- * 🏷️ Add or update types --> <!-- * ⚡️ Improve performance --> <!-- * _Other(s):_ ... --> <!-- [Impacts] Please provide a comma separated list of the potential impacts that might be introduced by this change --> <!-- * Generated values: Can your change impact any of the existing generators in terms of generated values, if so which ones? when? --> <!-- * Shrink values: Can your change impact any of the existing generators in terms of shrink values, if so which ones? when? --> <!-- * Performance: Can it require some typings changes on user side? Please give more details --> <!-- * Typings: Is there a potential performance impact? In which cases? -->
|
double
(#5215)double
Open in Stackblitz • @fast-check/examples @fast-check/ava
@fast-check/expect-type
fast-check
@fast-check/jest
@fast-check/packaged
@fast-check/poisoning
@fast-check/vitest
@fast-check/worker
commit: |
👋 A preview of the new documentation is available at: http://6786d03560e039fa2f2eb2cf--dubzzz-fast-check.netlify.app |
Description
When we first came up with the
double
arbitrary,bigint
were not mature enough in JavaScript. As such, we did not want our users to be forced to bump to the very last versions of Node and polyfilled it with out own 64bits bigint implementation.While it worked well and in an efficient way, it requires extra code and is probably less efficient (after further optimizations) than a native
bigint
. As such this PR drops it in favor of abigint
-based internal.What changes for the user? Well generated values, the shrinker. And for users blocked on legacy releases of Node (<10.5 or 10.4?), they might just not be able to use this major version of fast-check.
Checklist — Don't delete this checklist and make sure you do the following before opening the PR
yarn bump
and flag the impacts properlyAdvanced