> > Haskell' is about fixing existing practice, if it did go in, you > > would need some mechanism (i.e. class aliases) to ensure that it > > didn't break code.
> ... which is why we need class aliases!! > I want to see this change, *and* I want to see class aliases. :-) I want class aliases, and I want to see this change but *only if* we get class aliases. Functor =/=> Monad is annoying enough, we shouldn't make it worse without fixing the underlying limitation first. Ganesh ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== _______________________________________________ Haskell-prime mailing list Haskell-prime@haskell.org http://www.haskell.org/mailman/listinfo/haskell-prime
