How to get rid of IO
(Small text about that really FAQ)
|(One intermediate revision by one user not shown)|
Revision as of 09:19, 28 April 2009
1 QuestionI have something of type
How can I get that?
You can get rid of it, but we don't tell you how, since it is certainly not what need. It is the special safety belt of Haskell, 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 functionsusing atomic combinator functions like
These combinators are the great and elegant trick that allow to do something useful with IO functions while having all safety properties of a pure functional programming language. If that scares you, you can hide the combinator using the do notation, which will looks quite conveniently like:
do text <- readFile "foo" writeFile "bar" (someComplicatedNonIOOperation text)
Btw. using the combinators this would look like
writeFile "bar" . someComplicatedNonIOOperation =<< readFile "foo"
2.1 What we didn't tell you at the beginningBtw. The function that answers your initial question is
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