
This usecase is addressed by the fact that the haskell2010 and haskel98 packages would not be affected by this. If you need a largely static subset of Haskell there it is. -Edward On Wed, May 22, 2013 at 9:25 PM, Ivan Lazar Miljenovic < ivan.miljenovic@gmail.com> wrote:
On 23 May 2013 11:06, Casey McCann
wrote: On Wed, May 22, 2013 at 8:39 PM, Ivan Lazar Miljenovic
wrote: On 23 May 2013 07:32, Malcolm Wallace
wrote: -20 for generalising the Prelude +1 for removals from the Prelude -1 for adding monomorphic stuff +1000 for doing nothing
You are all nuts. :-)
I don't know if I'd go quite _that_ for as Malcolm for the weightings for the different proposals...
But I was speaking with a few other tutors of an introductory CS/programming course that uses Haskell (note: it's teaching programming with Haskell, not teaching Haskell per se: for example, all pattern matchings must be done with case statements as the lecturer considers top-level pattern matching a Haskell-specific quirk) about these proposals...
So in other words, your contention is that the design of the core library of Haskell should be driven by the needs of an introductory programming course, which is not even attempting to teach Haskell specifically, aimed at students who can't even figure out how tab characters work? That's marvelous.
I think you missed my point... I'm not saying it's just because of the course I'm tutoring, but that I disagree with the contention of "people learning Haskell will pick this up relatively easier so we should just dismiss anything about not generalising because it will make it easier for new people".
Also, not all people that learn Haskell are self-motivated in doing so, and thus won't take in the extra mental effort to understand how type-classes work right from the beginning.
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries