This repository has been archived by the owner on Jul 21, 2023. It is now read-only.
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.
both
inppx_let
is for concurrency but the current implementation forces sequential execution.Test
A concurrent applicative needs lazy evaluation. Since OCaml is strict the monad's type is a simple callback to the underlying type. The methods are straightforward except
apply
which awaits both callbacks concurrently. If its state is empty it stores the underlying value otherwise it applies both for the listener.bind
's tests expect callbacks to execute sequentially while theboth
's verify concurrency.Implementation
Adds
apply_both
to theApply
type class. It seemed perfect because of its symmetry toapply_first
. Formallyboth
is theMonoidal
equivalent ofapply
(commonly calledmerge
). I thoughtboth
would needpure
for liftedmap
but it worked without it. I also considered supplying overrides but it's tricky to implement lawfully.