Thanks. I'm okay with the status quo.. I just see it as a tradeoff. You are
giving up something to get something. In Python you give up any kind of
compile-time type checking, you give up the safety of immutable data, and
you get a whole lot of automatic type conversions and brief ways to express
certain algorithms. In Haskell you give up easy-to-comprehend error
messages and mutable data, and get back in reward a lot of reassurance that
your program does what you meant and expressivity. (I realize Haskell has
mutable data but it's not like Python's)
On Wed, Sep 19, 2012 at 7:43 PM, Ertugrul Söylemez
Notice: You probably forgot to apply `sin' to an argument.
However, I think that no work is done on that, and there is another possible path: An average Haskell tutorial should always include a section on understanding error messages. In fact the latest issue of The Monad Reader [1] has an article on that by Jan Stolarek.
[1]: http://themonadreader.files.wordpress.com/2012/08/issue20.pdf
Greets, Ertugrul
-- Not to be or to be and (not to be or to be and (not to be or to be and (not to be or to be and ... that is the list monad.
_______________________________________________ Beginners mailing list Beginners@haskell.org http://www.haskell.org/mailman/listinfo/beginners