Use the IO instance of MonadRandom #1677
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.
Fixes #1616.
Previously, block production had to live in STM, but this is no longer the
case as of #1445. This means that we no longer need to run
MonadRandom
computations in STM. To do that, we stored a DRG in a TVar.
Now, we can simply use IO's instance of
MonadRandom
. In the tests we stilluse the DRG-in-a-TVar trick, but we split it whenever we get a DRG.
We use the
RunMonadRandom
record for this purpose.Replace NodeState with MonadState
Previously, we need a separate
HasNodeState
class andNodeStateT
monadtransformer because there was already a
StateT
in our stack, i.e., the onecontaining the DRG. As that is gone, we can switch back to a regular
MonadState
+StateT
.The cost is an orphan instance:
MonadRandom (StateT s m)