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:
- The seven (more) deadly sins of microservices (in London on 27th September 2016)
- Well-Typed's Guide to the Haskell Type System (in London on 5th October 2016)
- Haskell eXchange Hackathon 2016 (in London on 8th - 9th October 2016)
- Fast Track to RESTful Microservices (in London on 2nd - 4th November 2016)
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