Re: Monad of no `return` Proposal (MRP): Moving `return` out of `Monad`

What about the derived functions in Control.Monad, such as liftM? Shall we similarly relax their constraints to Applicative and consider them "legacy"? (Did this already happen when I wasn't looking?) On Thursday, September 24, 2015, John Wiegley wrote:

...

...

...

...

...

Herbert Valerio Riedel javascript:;> writes:

...

TLDR: To complete the AMP, turn `Monad(return)` method into a top-level binding aliasing `Applicative(pure)`.

Very much +1.

John _______________________________________________ Libraries mailing list Libraries@haskell.org javascript:; http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries

-- -- Dan Burton