A Haskell function of type: IO String-> String

by

You can easily enough write a function that calls the readFile action, and passes the result to your index function.

readAndIndex fileName = do
    text <- readFile fileName
    return $ index text

However, the IO monad taints everything that uses it, so this function has the type:

readAndIndex :: FilePath -> IO [(String, [Integer])]

More Related Contents:

  1. Should do-notation be avoided in Haskell?
  2. Haskell: I/O and Returning From a Function
  3. Converting IO Int to Int
  4. In what sense is the IO Monad pure?
  5. What is a monad?
  6. Good examples of Not a Functor/Functor/Applicative/Monad?
  7. Applicatives compose, monads don’t
  8. Monads with Join() instead of Bind()
  9. What’s so bad about Lazy I/O?
  10. Wrong IO actions order using putStr and getLine
  11. IO happens out of order when using getLine and putStr
  12. What is indexed monad?
  13. Haskell read raw keyboard input
  14. Is Haskell truly pure (is any language that deals with input and output outside the system)?
  15. Euler 43 – is there a monad to help write this list comprehension?
  16. Why does haskell’s bind function take a function from non-monadic to monadic
  17. Expressing do block using only monadic bind syntax
  18. Why do we need monads?
  19. Difference between Monad and Applicative in Haskell
  20. Defining a new monad in haskell raises no instance for Applicative
  21. What is a monad?
  22. Is there a way to place some impure code inside pure functions?
  23. Concrete example showing that monads are not closed under composition (with proof)?
  24. Why are side-effects modeled as monads in Haskell?
  25. How to interpret bind/>>= of the function instance?
  26. Why should Applicative be a superclass of Monad?
  27. Haskell – depth for each node in binary tree using Reader monad
  28. How to return a pure value from a impure method
  29. How Monads are considered pure?
  30. Is Haskell’s mapM not lazy?

Leave a Comment