Xia Li-yao

I don't have access to a AVX-512 capable CPU either.

I don't know if we want this, but note that you can define `ifoldl'` using `Text.foldr` or `Text.foldl`. Or if you have it for lists, you can compose it with...

The main blocker for this proposal is going to be performance. I'd be surprised if you can use your API to write a streaming JSON parser whose performance is comparable...

I concede that you can get your data structure to be inlined. But that relies on unrolling the loop yourself so you always start an iteration at a code point...

Having conceded that performance is not an issue, the only remaining difference with `Data.Text.Internal.Encoding.Utf8` I see is that your API lets you not have any parser state (except the offset)...

I'm just making sure that I'm not completely missing the point of your proposal. Beyond that, we'll indeed have to agree to disagree, unless another @haskell/text maintainer wants to chime...

I added some tests and rebased. To answer some of the questions: > Can QuickCheck generate monadic functions? We could but we don't need to. Because of `foldlM`'s polymorphism, we...

Fixed by inspection-testing `S.foldlM'` instead of `T.foldlM'` (which is a wrapper around it, and with the `+developer` flag there's a `HasCallstack` constraint that confuses `inspection-testing`.)

That may be the right fix for now, but it's worth noting it's only a temporary fix. Is there a longer term solution? The root of the problem is that...

Maybe with `foldr`?