Make default reduceMapM lazy if reduceRightTo is lazy #3167
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.
Currently
foldMapM
andfoldMapA
will be lazy if the operations they're built on are sufficiently lazy, butreduceMapM
isn't.Take the following stand-alone non-empty stream implementation (I'm not using
NonEmptyStream
becauseStream
'sreduceRightToOption
isn't lazy enough, which should probably be a separate issue):Compare
foldMapM
,foldMapA
, andreduceMapM
:With the implementation here it works fine:
It's worth noting that this new implementation doesn't require
FlatMap
, which is one of the things #3150 is addressing via a newreduceMapA
. If someone has a lazy implementation using theFlatMap
that would be more efficient (similar tofoldMapM
vs.foldMapA
), I'd be happy to use it, but I couldn't come up with one.