"Manuel M. T. Chakravarty" wrote:
> * I am not a big fan of introducing an extra monad (`GUI' in
> this case). It can easily become a pain in programs that
> do a lot of "normal" IO as you have to lift all IO
> functions to GUI.
Shouldn't GUI be a typeclass (as a subclass of Monad), with IO being an
instance of it? This gives the following benefits:
o "Pure" GUI functions can reflect this in their type.
i.e. (GUI g) => g ()
o IO functions can use GUI features directly without lifting.
o "Pure" GUI functions are implicitly usable in the IO monad
They "are" IO functions.
Regards,
Matt
_______________________________________________
Haskell mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/haskell
- RE: GUI Library Task Force Simon Peyton-Jones
- RE: GUI Library Task Force Manuel M. T. Chakravarty
- RE: GUI Library Task Force S. Alexander Jacobson
- Re: GUI Library Task Force Ian Lynagh
- Re: GUI Library Task Force Manuel M. T. Chakravarty
- RE: GUI Library Task Force Matt Harden
- RE: GUI Library Task Force Peter Achten
- Re: GUI Library Task Force Sengan
- RE: GUI Library Task Force Ashley Yakeley
- RE: GUI Library Task Force S. Alexander Jacobson
- Re: GUI Library Task Force Tim Sauerwein
- Re: GUI Library Task Force Lennart Augustsson
- Re: GUI Library Task Force S. Alexander Jacobson
- Re: GUI Library Task Force Lennart Augustsson
- Re: GUI Library Task Force Ketil Malde
- Namespaces (was Re: GUI Library Task For... Hal Daume III
