Status of #10071 (class method deprecations)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Status of #10071 (class method deprecations)

Fumiaki Kinoshita
I stumbled upon a case where I want to deprecate a class method in favour of another (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? 

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: Status of #10071 (class method deprecations)

Richard Eisenberg-5
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 <[hidden email]> 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), 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? 
_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs