My take (not authoritative) is that some good ideas were floated, but nothing was decided on. Given that we now have a proper process for deciding on new features, I think we should use it, and go via a proposal. Note that I've fixed the link in the original description to point to https://gitlab.haskell.org/ghc/ghc/-/wikis/design/deprecation-mechanisms/type-class-methods
Richard > On Nov 6, 2020, at 1:22 AM, Fumiaki Kinoshita <fumiex...@gmail.com> wrote: > > I stumbled upon a case where I want to deprecate a class method in favour of > another (https://github.com/fumieval/witherable/pull/68 > <https://github.com/fumieval/witherable/pull/68>), which reminded me of some > discussion around Monad-of-no-return proposal. > > There seems to be an old ticket, but I'm not sure what the status is -- > is this approved and waiting for implementation, or something which needs to > be resubmitted to ghc-proposals? > https://gitlab.haskell.org/ghc/ghc/-/issues/10071 > <https://gitlab.haskell.org/ghc/ghc/-/issues/10071> > _______________________________________________ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
