3 ms·
The author makes a nice case for lazy evaluation, but I doubt the "goal to help experienced procedural programmers make the transition to Haskell" is achieved
by Luyt 17y ago
The author makes a nice case for lazy evaluation, but I doubt the "goal to help experienced procedural programmers make the transition to Haskell" is achieved because he doesn't explain how to read special Haskell constructs:
mapM_ (interactFile (unlines . map processIt . lines)) args
ss <- mapM readFile fileNames
putStr $ f (concat ss)
A c++ programmer might ask: What do these dots means? Wat does the $ character do? Why us mapM sometimes used with and without trailing underscore?
It seems like one should learn Haskell first, before being able to understand the examples.
- jberryman 17y agoThe article is billed as a tutorial on haskell IO, so I presume a knowledge of haskell syntax as basic as (.) and ($) is assumed. But I agree that this probably isn't such an effective introduction to IO or haskell.