Apologies, that wasn't finished. I meant to say, does it mean that by writing a BMonad instance a Monad instance would be automatically generated? If so, that seems like it would cause conflicts in many cases. Regardless, I think "newclass" needs to be better specified if you want other people to be able to support it.
On Thu, Oct 3, 2013 at 7:53 PM, John Lato <jwl...@gmail.com> wrote: > I don't really understand what a "newclass" is supposed to be. > > > On Thu, Oct 3, 2013 at 2:15 PM, Wvv <vite...@rambler.ru> wrote: > >> >> newclass Bind a => Monad a => BMonad a where { (>>=) = (>>-) } > > > I think this means that `BMonad` is supposed to be a new class that has > both Bind and Monad in scope, the same as > > class (Bind a, Monad a) => BMonad a > > except that the Monad instance's (>>=) is replaced by (>>-). > > If that's what "newclass" means, it seems absolutely pointless. > > Does it instead mean that one could write > > instance Bind MyType where > > instance BMonad MyType >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe