How to get rid of IO
(Small text about that really FAQ)
m (→Answer: copy editing: fix whitespace, remove acronyms, remove value judgments, correct grammar)
|(2 intermediate revisions by one user not shown)|
Latest revision as of 15:17, 8 March 2013
 1 QuestionI have something of type
How can I get that?
 2 AnswerYou can get rid of it, but you almost certainly don't need to. The special safety belt of Haskell is that you cannot get rid of IO! Nonetheless, the biggest parts of Haskell programs are and should be non-IO functions. Applications using both IO and non-IO functions are written by plugging together these two flavors of functions using functions like
You can hide some functions using do notation, which looks like this:
do text <- readFile "foo" writeFile "bar" (someComplicatedNonIOOperation text)
Without hiding the functions, this would look like:
writeFile "bar" . someComplicatedNonIOOperation =<< readFile "foo"
 2.1 What we didn't tell you at the beginningThere is a function which directly answers the initial question, namely,
It must only be used to wrap IO functions that behave like non-IO functions,Since this property cannot be checked by the compiler, it is your task and thus the
(Some library writers have abused that name component for partial functions. Don't get confused!) You will only need this in rare cases and only experienced programmers shall do this.
 3 See also
- Introduction to IO
- Avoiding IO - Avoiding IO in the first place is a good thing, and we tell you how to achieve that
- Tackling the awkward squad