Michael Snoyman wrote:Ok, I now have:
> Sorry, I should have been more clear. I was referring to the flush[1] from
> blaze-builder. So your code would look something like:
>
> map (\bs -> fromByteString bs <> flush)
>
> As an aside, you might want to look at using mapOutput[2] which avoids an
> intermediate data structure.
mapOutput (\bs -> fromByteString bs `mappend` flush) $ requestBody req
and still have the same problem, which I now suspect must lie elsewhere.
I think it does. It would be nice to write idiomatic conduit code and have
> In fact, I wonder if a rewrite rule would make sense here.
GHC compile it to be as optimal as possible.