<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>conduit-0.2.2: Streaming data processing library.</title><link href="ocean.css" rel="stylesheet" type="text/css" title="Ocean" /><script src="haddock-util.js" type="text/javascript"></script><script type="text/javascript">//<![CDATA[
window.onload = function () {pageLoad();};
//]]>
</script></head><body><div id="package-header"><ul class="links" id="page-menu"><li><a href="index.html">Contents</a></li><li><a href="doc-index.html">Index</a></li></ul><p class="caption">conduit-0.2.2: Streaming data processing library.</p></div><div id="content"><div id="description" class="doc"><h1>conduit-0.2.2: Streaming data processing library.</h1><p>Conduits are an approach to the streaming data problem. It is meant as an alternative to enumerators/iterators, hoping to address the same issues with different trade-offs based on real-world experience with enumerators. For more information, see <a href="http://www.yesodweb.com/book/conduit">http://www.yesodweb.com/book/conduit</a>.
</p><p>Release history:
</p><dl><dt>0.2</dt><dd> Instead of storing state in mutable variables, we now use CPS. A <code>Source</code> returns the next <code>Source</code>, and likewise for <code>Sink</code>s and <code>Conduit</code>s. 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 <code>Prepared</code> set of types. Also, the <code>State</code> functions (e.g., <code>sinkState</code>) use better constructors for return types, avoiding the need for a dummy state on completion.
</dd><dt>0.1</dt><dd> <code>BufferedSource</code> is 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 <code>BufferedSource</code> being a specific tool used internally as needed, but using <code>Source</code> for all external APIs.
</dd><dt>0.0</dt><dd> Initial release.
</dd></dl></div><div id="module-list"><p class="caption">Modules</p><ul><li><span id="control.n.1" class="module collapser" onclick="toggleSection('n.1')">Control</span><ul id="section.n.1" class="show"><li><span id="control.n.1.1" class="module collapser" onclick="toggleSection('n.1.1')">Monad</span><ul id="section.n.1.1" class="show"><li><span id="control.n.1.1.1" class="module collapser" onclick="toggleSection('n.1.1.1')">Trans</span><ul id="section.n.1.1.1" class="show"><li><span class="module"><a href="Control-Monad-Trans-Resource.html">Control.Monad.Trans.Resource</a></span></li></ul></li></ul></li></ul></li><li><span id="control.n.2" class="module collapser" onclick="toggleSection('n.2')">Data</span><ul id="section.n.2" class="show"><li><span class="module"><span id="control.n.2.1" class="collapser" onclick="toggleSection('n.2.1')"> </span><a href="Data-Conduit.html">Data.Conduit</a></span><ul id="section.n.2.1" class="show"><li><span class="module"><a href="Data-Conduit-Binary.html">Data.Conduit.Binary</a></span></li><li><span class="module"><a href="Data-Conduit-Lazy.html">Data.Conduit.Lazy</a></span></li><li><span class="module"><a href="Data-Conduit-List.html">Data.Conduit.List</a></span></li><li><span class="module"><a href="Data-Conduit-Text.html">Data.Conduit.Text</a></span></li></ul></li></ul></li></ul></div></div><div id="footer"><p>Produced by <a href="http://www.haskell.org/haddock/">Haddock</a> version 2.9.2</p></div></body></html>
