Haskell is one of the few programming languages that use lazy evaluation: computations get performed only when their result is demanded. It is however not so straightforward to combine lazy evaluation with side effects, such as reading from a file.
Lazy I/O is the standard solution to this in the current base libraries, but has its problems. We explain how lazy I/O works, what the problems are, and explore some of the solutions that are being proposed at the moment: iteratees, pipes, stream I/O, etc.
YOU MAY ALSO LIKE:
- Scrum - The Good, The Bad and The Not So Good (in London on 3rd December 2015)
- Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 7th - 9th December 2015)
- Scala eXchange 2015 (in London on 10th - 11th December 2015)
- Uncle Bob's TDD and Refactoring (in London on 10th - 11th December 2015)
Lazy I/O and Alternatives in Haskell
Edsko joined Well-Typed as a Haskell Consultant in 2012. He is one of the primary authors of Cloud Haskell and has recently been working on Haskell language infrastructure.Edsko has been using Haskell since 2004, and holds a PhD in substructural type