-
Notifications
You must be signed in to change notification settings - Fork 52
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
Tuple instances random #72
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should add features related to Random
. To use these, people need to change their code anyway. I think it would be better for them to switch to using UniformRange
, which already has tuple instances.
This feels like encouraging users to adopt / keep using Random
.
UniformRange doesn't have tuple instances. And couldn't possibly have |
You are right of course. |
@curiousleo This has already been discussed in #26 and it was also pointed out here that
We've discussed this on multiple occasions. |
@lehins since now we have instances for tuples both in |
I'll extract some tests from this PR and will use it to compare performance of derived vs manual instances for tuples. I'll keep it open just for the time being so I don't forget to do it. |
758afba
to
01ee33f
Compare
5caac2c
to
a30b4c9
Compare
* Fix range for floating point from `[0, 1)` to `[0, 1]` * Remove promise of uniform values for all types * Add notes to individual instances with their peculiarities
a30b4c9
to
a850570
Compare
Fix for: #26
Instances for tuples. Improved coverage. Fixes to
Random
haddock.