There is a painfully long chain of discussions on fixing the instance Applicative m => Monad m situation. 

I'd love to see that resolved as well! 

But I'd rather not tie all good things in the Haskell ecosystem to the one thing we've repeatedly demonstrated our lack of ability to accomplish. =(

-Edward


On Wed, May 22, 2013 at 6:22 PM, Ross Paterson <R.Paterson@city.ac.uk> wrote:
On Wed, May 22, 2013 at 01:12:11PM +0100, Ian Lynagh wrote:
> I think there are 4 things it has been suiggested that we might do:
> * Generalise Prelude.mapM etc
> * Remove Prelude.mapM etc
> * Add more monomorphic variants to Prelude (e.g. whenJust)
> * Nothing

Wasn't there also mention of making Applicative a superclass of Monad?

That might actually have less impact on beginners than generalizing the
types of foldr and sum, and doing it first might allow us to rationalize
the situation with some of the monad combinators that are clashing.

_______________________________________________
Libraries mailing list
Libraries@haskell.org
http://www.haskell.org/mailman/listinfo/libraries