Re:Why the world needs Haskell
by nilkn on Tuesday July 09, 2013 @07:02PM
(#6016283)
Monads don't really have much to do with IO. It's up in the air whether IO really even is a monad. See Conal Elliot's answer on SO and the link he provides: http://stackoverflow.com/a/16444789/65799
[ Parent
| on HN ]
You mean...all this time... !
Reminds me of the story of the old monk who emerges from the basement of the monestary holding an ancient parchment. Tears are streaming down his face. The student asks "What's wrong?" The old monk replies "All this time! We were supposed to be celebRate!"
A thing that people are often unaware of when trying to understand how the IO type works in Haskell is that you cannot define the IO type in Haskell.
Sure you can: http://hackage.haskell.org/packages/archive/ghc-prim/0.2.0.0...
You can't define RealWorld, though, nor (IIRC) is IO really a state monad.
I used "define" imprecisely.
You cannot, so far as I know, implement `>>=` for the IO type defined in the above link within Haskell, which means you can't actually use it to do IO.
Re:Why the world needs Haskell
by applicative on Wednesday July 10, 2013 @07:35PM
(#6023551)
Here's another definition -- by continuation -- from Hug's Prelude (http://cpansearch.perl.org/src/AUTRIJUS/Language-Haskell-0.0...) :
newtype IO a = IO ((a -> IOResult) -> IOResult)
data IOResult
= Hugs_ExitWith Int
| Hugs_Catch IOResult (Exception -> IOResult) (Obj -> IOResult)
| Hugs_ForkThread IOResult IOResult
| Hugs_DeadThread
| Hugs_YieldThread IOResult
| Hugs_Return Obj
| Hugs_BlockThread (Obj -> IOResult) ((Obj -> IOResult) -> IOResult)