This repository has been archived by the owner on Dec 12, 2021. It is now read-only.
Make Effect
& EffectMapping
a monoid structure
#20
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.
This PR adds
Effect
,Mapping
, andEffectMapping
conforming to Monoid structure (2 instances are combine-able with associativity and has identity) for better composition.Please note that
EffectMapping
will now have multiple ways of conforming to Monoid since its internal structure isInput -> State -> (State, Effect)?
returningOptional
as the architectural choice.Because of this,
static func reduce
will now introduceenum ReduceStrategy { case first, all, tryAll }
for various reducing strategies.(Previously, this reducing strategy was assumed to have
.first
only (picking one of the mapping from array), but this prevents from sibling mappings composition, so having.all
is essentially needed to behave just as same behavior asInput -> State -> (State, Effect)
which returnsIdentity(Monad)
.