conduit: Streaming data processing library.
conduit is a solution to the streaming data problem, allowing for production, transformation, and consumption of streams of data in constant memory. It is an alternative to lazy I/O which guarantees deterministic resource handling, and fits in the same general solution space as
pipes. For a tutorial, please visit https://haskell.fpcomplete.com/user/snoyberg/library-documentation/conduit-overview.
- Simplified the user-facing interface back to the Source, Sink, and Conduit types, with Producer and Consumer for generic code. Error messages have been simplified, and optional leftovers and upstream terminators have been removed from the external API. Some long-deprecated functions were finally removed.
- The internals of the package are now separated to the .Internal module, leaving only the higher-level interface in the advertised API. Internally, switched to a
Leftoverconstructor and slightly tweaked the finalization semantics.
- Inspired by the design of the pipes package: we now have a single unified type underlying
Conduit. This type is named
Pipe. There are type synonyms provided for the other three types. Additionally,
BufferedSourceis no longer provided. Instead, the connect-and-resume operator,
$$+, can be used for the same purpose.
- ResourceT has been greatly simplified, specialized for IO, and moved into a separate package. Instead of hard-coding ResourceT into the conduit datatypes, they can now live around any monad. The Conduit datatype has been enhanced to better allow generation of streaming output. The SourceResult, SinkResult, and ConduitResult datatypes have been removed entirely.
- Instead of storing state in mutable variables, we now use CPS. A
Sourcereturns the next
Source, and likewise for
Conduits. Not only does this take better advantage of GHC's optimizations (about a 20% speedup), but it allows some operations to have a reduction in algorithmic complexity from exponential to linear. This also allowed us to remove the
Preparedset of types. Also, the
sinkState) use better constructors for return types, avoiding the need for a dummy state on completion.
BufferedSourceis now an abstract type, and has a much more efficient internal representation. The result was a 41% speedup on microbenchmarks (note: do not expect speedups anywhere near that in real usage). In general, we are moving towards
BufferedSourcebeing a specific tool used internally as needed, but using
Sourcefor all external APIs.
- Initial release.
experimental code to use raw system calls in place of handles. Not recommended for general use
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.
For package maintainers and hackage trustees