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

⚡️ Drop unneeded BigInt check in mixedCase #5612

Merged
merged 2 commits into from
Jan 14, 2025
Merged

⚡️ Drop unneeded BigInt check in mixedCase #5612

merged 2 commits into from
Jan 14, 2025

Conversation

dubzzz
Copy link
Owner

@dubzzz dubzzz commented Jan 14, 2025

Description

While not being really expensive to compute it's yet another check and dropping it could be useful if we want to go faster. Indeed with BigInt being a thing in Node since 10.5.0, we probably don't want to pay for checking it all the time.

We will probably have to bump our minimal requirement to 10.5.0+ for the version 4 of fast-check so that we can expect it to always be a thing no matter the runtime being used as long as it fits our requirements.

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: No

Sorry, something went wrong.

**Description**

<!-- Please provide a short description and potentially linked issues
justifying the need for this PR -->

While not being really expensive to compute it's yet another check and
dropping it could be useful if we want to go faster. Indeed with
`BigInt` being a thing in Node since 10.5.0, we probably don't want to
pay for checking it all the time.

We will probably have to bump our minimal requirement to 10.5.0+ for the
version 4 of fast-check so that we can expect it to always be a thing no
matter the runtime being used as long as it fits our requirements.

<!-- * 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: No

<!-- [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

🦋 Changeset detected

Latest commit: f6799b7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
fast-check Minor

Not sure what this means? Click here to learn what changesets are.

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

@dubzzz dubzzz changed the title ⚡️ Drop unneeded BigInt check in mixedCase (#5211) ⚡️ Drop unneeded BigInt check in mixedCase Jan 14, 2025

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
@dubzzz dubzzz enabled auto-merge (squash) January 14, 2025 19:45
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@5612

@fast-check/expect-type

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

fast-check

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

@fast-check/jest

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

@fast-check/packaged

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

@fast-check/poisoning

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

@fast-check/vitest

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

@fast-check/worker

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

commit: f6799b7

Copy link

codecov bot commented Jan 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.80%. Comparing base (40a23e1) to head (f6799b7).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5612      +/-   ##
==========================================
+ Coverage   94.77%   94.80%   +0.02%     
==========================================
  Files         235      235              
  Lines       10034    10031       -3     
  Branches     2825     2825              
==========================================
  Hits         9510     9510              
+ Misses        524      521       -3     
Flag Coverage Δ
unit-tests 94.80% <ø> (+0.02%) ⬆️
unit-tests-18.x-Linux 94.80% <ø> (+0.02%) ⬆️
unit-tests-20.x-Linux 94.80% <ø> (+0.02%) ⬆️
unit-tests-22.x-Linux 94.80% <ø> (+0.02%) ⬆️
unit-tests-latest-Linux 94.80% <ø> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

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

@dubzzz dubzzz merged commit c2f0e52 into main Jan 14, 2025
57 checks passed
@dubzzz dubzzz deleted the pr-5211 branch January 14, 2025 20:07
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.

None yet

1 participant