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:
- Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 9th - 10th March 2017)
- Test all the things with Intern 4 with Dylan Schiemann! (in London on 15th March 2017)
- DDD eXchange 2017 (in London on 27th - 28th April 2017)
- Gáspár Nagy's Developing with SpecFlow (in London on 28th - 30th June 2017)
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