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.
Closes #178 and #362
Depends on PR #436
This PR implements
spanM
(span from the left) andspanEndM
(span from the right) for both strict and lazyText
.spanM
is a combination ofspan
andfoldr
.spanM
, as its name indicates, generalizesspan
, with a monadic predicate, of typeChar -> m Bool
rather thanChar -> Bool
.spanM
generalizes a short-circuitingfoldr
, by also remembering the location where it stopped so you can easily resume with another search from there.spanM
can also implementfoldl'
with the same space and time efficiency, by making the predicate alwaysTrue
and only using the state effect.I argue these two functions pass the Fairbairn threshold as they provide the ability to safely move back and forth inside a
Text
. As mentioned in #178, this is currently not possible to do both efficiently and safely: either you keep track of an offset in code points, which then requires a redundant traversal to dosplitAt
, or you keep track of an offset in bytes, which is unsafe.With
spanM
one can easily implement atakeWhileM
(#362) by ignoring the remaining suffix. I'm not sure if its allocation would be optimized out already, but if not, I can generalize `spanM`` with some continuation-passing trick to do that in a future PR.