Alternative usage of random
#84
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also implement support for
random-1.3
This is an equivalent approach in the sense of semantics, but very different in how it is achieved.
Instead of defining
CapGenM
this PR utilizes an existingStateGenM
provided byrandom
package. The two things that were missing in order for us to be able to useStateGenM
was missing instances:MonadState
(frommtl
) forM
RandomGen
forGenState
I am not sure whether others will find this approach cleaner or easier to understand, but if we want to continue using the older approach, then #85 implements support for
random-1.3
that also includes one of the simplifications present in this PR, namely removal offakeSeed