streaming 0.1.0.14 → 0.1.0.15
raw patch · 1 files changed
+14/−13 lines, 1 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- streaming.cabal +14/−13
streaming.cabal view
@@ -1,10 +1,10 @@ name: streaming-version: 0.1.0.14+version: 0.1.0.15 cabal-version: >=1.10 build-type: Simple synopsis: a free monad transformer optimized for streaming applications -description: `Stream` can be used wherever `FreeT` is used. The compiler's+description: @Stream@ can be used wherever @FreeT@ is used. The compiler's standard range of optimizations work better for operations written in terms of `Stream`. @FreeT f m r@ / @Stream f m r@ is of course extremely general, and many functor-general combinators@@ -23,20 +23,21 @@ . and the like. @Streaming.Prelude@ closely follows @Pipes.Prelude@, but cleverly /omits the pipes/: .- >>> S.stdoutLn $ S.take 2 S.stdinLn- let's<Enter>- let's- stream<Enter>- stream+ + > ghci> S.stdoutLn $ S.take 2 S.stdinLn+ > let's<Enter>+ > let's+ > stream<Enter>+ > stream . And here we do a little /connect and resume/, as the streaming-io experts call it: .- >>> rest <- S.print $ S.splitAt 3 $ S.each [1..10]- 1- 2- 3- >>> S.sum rest- 49+ > ghci> rest <- S.print $ S.splitAt 3 $ S.each [1..10]+ > 1+ > 2+ > 3+ > ghci> S.sum rest+ > 49 . Somehow, we didn't even need a four-character operator for that, nor advice about best practices; just ordinary Haskell common sense.