You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I received a PR recently which used vectorBuilder to produce ByteStrings (via conversion from unboxed vectors). I was surprised when I looked at the source code that it does not produce vectors lazily, and instead produces the list of vectors and yields them all once the conduit has finished. Is this expected behaviour? It's certainly surprising to me given its type!
The text was updated successfully, but these errors were encountered:
It's honestly been so long since I wrote this that I don't remember. From the code and comments, it looks like it's designed to handle a very specific kind of inefficiency we were running into at the time, and may in fact not stream the output as you're anticipating.
I received a PR recently which used
vectorBuilder
to produce ByteStrings (via conversion from unboxed vectors). I was surprised when I looked at the source code that it does not produce vectors lazily, and instead produces the list of vectors and yields them all once the conduit has finished. Is this expected behaviour? It's certainly surprising to me given its type!The text was updated successfully, but these errors were encountered: