lazyio 0.0.3.1 → 0.0.3.2
raw patch · 2 files changed
+9/−8 lines, 2 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- lazyio.cabal +4/−3
- src/System/IO/Lazy.hs +5/−5
lazyio.cabal view
@@ -1,5 +1,5 @@ Name: lazyio-Version: 0.0.3.1+Version: 0.0.3.2 License: BSD3 License-File: LICENSE Author: Henning Thielemann <haskell@henning-thielemann.de>@@ -13,7 +13,8 @@ which is however driven by its output. That is, the LazyIO action is only executed as far as necessary in order to provide the required data.-Tested-With: GHC==6.8.2+Tested-With: GHC==6.8.2, GHC==6.12.1+Tested-With: GHC==7.4.1 Cabal-Version: >=1.6 Build-Type: Simple Source-Repository head@@ -23,7 +24,7 @@ Source-Repository this type: darcs location: http://code.haskell.org/~thielema/lazyio/- tag: 0.0.3.1+ tag: 0.0.3.2 Flag splitBase description: Choose the new smaller, split-up base package.
src/System/IO/Lazy.hs view
@@ -9,7 +9,7 @@ which is considered safe for interleaving I/O actions. - Operations like 'System.IO.hClose' are usually not safe within this monad,- since they will only executed, if their result is consumed.+ since they will only get executed, if their result is consumed. Since this result is often @()@ this is quite unusual. It will also often be the case, that not the complete output is read, and thus the closing action is never reached.@@ -20,6 +20,9 @@ The first one does not trigger previous IO actions, whereas the second one does. +- We advise to lift strict IO functions into the lazy IO monad.+ Lifting a function like @readFile@ may lead to unintended interleaving.+ Use it like > import qualified System.IO.Lazy as LazyIO@@ -31,11 +34,8 @@ > y <- liftIO getLine > return x -Because only the first line is needed,+Because only the first entered line is needed, only the first prompt and the first 'getLine' is executed.--We advise to lift strict IO functions into the lazy IO monad.-Lifting a function like @readFile@ may lead to unintended interleaving. -} module System.IO.Lazy ( T,