Fix Either
and Maybe
::memoize()
not loading everything
#31
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.
Problem
When one creates a deferred
Maybe
and then compose it via aflatMap
that returns a new deferredMaybe
this creates internally a deferred monad containing a deferred monad. When the methodmemoize
is called on it, it returns the underlying deferred monad.This is problematic because the user thinks the whole composition has been memoized and potential IO operations associated with it have been done. But this is not the case.
The same problem happens with
Either
.Solution
When
memoize
is called on these monads it recursivelymemoize
the underlying monad. This way the recursion stops when a non deferred monad is found.