More Conduit.Binary lazy ByteString functions

[snoyberg]

More Conduit.Binary lazy ByteString functions

[snoyberg]

I'm not sure what these functions would be exactly, can you give me a sample type signature?

[nh2]

The same as in http://hackage.haskell.org/package/conduit-1.0.8/docs/Data-Conduit-Binary.html, with lazy ByteStrings:

-- Existing:
sinkFile :: MonadResource m => FilePath -> Consumer ByteString m ()
sinkHandle :: MonadIO m => Handle -> Consumer ByteString m ()
sinkIOHandle :: MonadResource m => IO Handle -> Consumer ByteString m ()

-- What I mean:
sinkFileLbs :: MonadResource m => FilePath -> Consumer L.ByteString m ()
sinkHandleLbs :: MonadIO m => Handle -> Consumer L.ByteString m ()
sinkIOHandleLbs :: MonadResource m => IO Handle -> Consumer L.ByteString m ()

[snoyberg]

In that case, I'm not sure what the connection to sinkLbs is, or where a full copy would be implied. I would think that the natural way to address this would be something like:

unlazyConduit :: Monad m => Conduit L.ByteString m S.ByteString
unlazyConduit = Data.Conduit.List.concatMap L.toChunks

But it's hard for me to imagine a situation where you would ever be dealing with a stream of lazy bytestrings, can you clarify how that arises?

[nh2]

But it's hard for me to imagine a situation where you would ever be dealing with a stream of lazy bytestrings, can you clarify how that arises?

I meant it only as a convenience for libraries which operate only on lazy bytestrings; at the momment, I have to map them to lazy myself. In general, I agree that streaming takes away the need for lazyness.