Comments on: Playing unsafe haskell

By: Is There a Such Thing as Real World Haskell? « The Other Librarian

Is There a Such Thing as Real World Haskell? « The Other Librarian — Wed, 08 Sep 2010 16:54:32 +0000

[...] tests should include the System.IO.Unsafe module (cheating should be allowed when you are testing your code – let the learning happen when you [...]

By: Magnus

Magnus — Wed, 09 May 2007 09:48:04 +0000

Alan,

That's a very good point. I've found that quite a few standard functions are "lazy enough", just like getContents.

Thanks for the link to FRP!

By: Alan Falloon

Alan Falloon — Mon, 07 May 2007 16:21:20 +0000

If your event stream is actually the characters of stdin, then getContents already hides the details of the unsafeInterleaveIO for you. As in:

getContents >>= mapM_ yourFunc . takeWhile (/= 'q')

However, understanding the internals makes it possible to generalize this approach to one where the event stream contains richer data (such as GUI events).

Perhaps there is more that can be learned from FRP (functional reactive programming)