You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we started fast-check, we explicitly made a distinction between synchronous and asynchronous properties.
At that point in time, asynchronous code was slower to execute and thus making it the default would not have been great performance-wise. It was also way less idiomatic than today. And no direct integration of fast-check to Jest or Vitest or Ava ever existed.
Now the performance point seems negligeable, the DX one too when using one of our integrations. The only possibly remaining blocker is when using fast-check without any dedicated integration. Dropping the dual thing would drop code, simplify async usages...
In terms of performance, here is what we measured against the 3.22:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When we started fast-check, we explicitly made a distinction between synchronous and asynchronous properties.
At that point in time, asynchronous code was slower to execute and thus making it the default would not have been great performance-wise. It was also way less idiomatic than today. And no direct integration of fast-check to Jest or Vitest or Ava ever existed.
Now the performance point seems negligeable, the DX one too when using one of our integrations. The only possibly remaining blocker is when using fast-check without any dedicated integration. Dropping the dual thing would drop code, simplify async usages...
In terms of performance, here is what we measured against the 3.22:
Beta Was this translation helpful? Give feedback.
All reactions