Monad of no `return` Proposal (MRP): Moving `return` out of `Monad`
danburton.email at gmail.com
Fri Sep 25 00:36:04 UTC 2015
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 <johnw at newartisans.com> wrote:
> > TLDR: To complete the AMP, turn `Monad(return)` method into a
> > top-level binding aliasing `Applicative(pure)`.
> Very much +1.
> Libraries mailing list
-- Dan Burton
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libraries