-
Notifications
You must be signed in to change notification settings - Fork 104
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
Bump version bound for QuickCheck 2.13 #410
Comments
@nick8325 there seems to be something fishy. Given
I observe that
vs
Is this expected? |
This is really strange. I hadn't thought about making The weird thing is that this works with |
Oops:
It looks like the problem only occurs with |
My initial impression is that this bug shouldn't worsen testing, at least, because a seed in QuickCheck is either split or applied to |
@nick8325 there is more. Apparently
With
vs
|
@snoyberg @alexeyzab I can't comment on commercialhaskell/stackage#4444. |
@sol 👍 |
@sol Both of those should be fixed now. Let me know if you're happy for me to make a new release. |
Ah wait, not sure that it's working yet. I'll report back... |
There, that should be actually fixed now. |
@nick8325 looks good now. Let me know once it's on Hackage._ |
There, 2.13.1 is now on Hackage! |
On Hackage, closing. |
I just released QuickCheck 2.13. There are no major API changes and Hspec at least builds with it (I haven't run it) but at least the version bounds will need relaxing.
It also uses
splitmix
rather thantf-random
for random number generation, which perhaps makes #406 obsolete.The text was updated successfully, but these errors were encountered: