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

⚡️ Faster rewrite of double #5618

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

⚡️ Faster rewrite of double #5618

wants to merge 2 commits into from

Conversation

dubzzz
Copy link
Owner

@dubzzz dubzzz commented Jan 14, 2025

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

ChecklistDon't delete this checklist and make sure you do the following before opening the PR

  • The name of my PR follows gitmoji specification
  • My PR references one of several related issues (if any)
    • New features or breaking changes must come with an associated Issue or Discussion
    • My PR does not add any new dependency without an associated Issue or Discussion
  • My PR includes bumps details, please run yarn bump and flag the impacts properly
  • My PR adds relevant tests and they would have failed without my PR (when applicable)

Advanced

  • Category: ⚡️ Improve performance
  • Impacts: Generated values, shrinker, minimal requirements for Node

**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?
-->
Copy link

changeset-bot bot commented Jan 14, 2025

⚠️ No Changeset found

Latest commit: 76ed7ee

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dubzzz dubzzz changed the title ⚡️ Faster rewrite of double (#5215) ⚡️ Faster rewrite of double Jan 14, 2025
Copy link

pkg-pr-new bot commented Jan 14, 2025

Open in Stackblitz@fast-check/examples

@fast-check/ava

npm i https://pkg.pr.new/@fast-check/ava@5618

@fast-check/expect-type

npm i https://pkg.pr.new/@fast-check/expect-type@5618

fast-check

npm i https://pkg.pr.new/fast-check@5618

@fast-check/jest

npm i https://pkg.pr.new/@fast-check/jest@5618

@fast-check/packaged

npm i https://pkg.pr.new/@fast-check/packaged@5618

@fast-check/poisoning

npm i https://pkg.pr.new/@fast-check/poisoning@5618

@fast-check/vitest

npm i https://pkg.pr.new/@fast-check/vitest@5618

@fast-check/worker

npm i https://pkg.pr.new/@fast-check/worker@5618

commit: 0986e37

Copy link
Contributor

👋 A preview of the new documentation is available at: http://6786d03560e039fa2f2eb2cf--dubzzz-fast-check.netlify.app

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

Successfully merging this pull request may close these issues.

1 participant