[ghc-steering-committee] #380 GHC2021: MonadFailDesugaring

[Simon Marlow]

I don't think MonadFailDesugaring should have been part of the GHC2021
discussion at all - it's part of an existing migration plan, and there's no
reason to disrupt that with GHC2021. That's why I labeled it "irrelevant"
in my vote.

Cheers
Simon

On Thu, 24 Dec 2020 at 14:25, Joachim Breitner <mail at joachim-breitner.de>
wrote:

> Hi,
>
> mostly a technical point, but just to avoid confusion
>
> MonadFailDesugaring is already on by default, and according to the
> docs, is supposed to be deprecated, _but making that behaviour
> permanent_. (So, really, NoMonadFailDesugaring is what is being
> deprecated).
>
> I was previously confused by this and voted for “no”, which is not what
> my intention is.  I updated my vote to “yes”.
>
> This now has 7 votes and reached “barely out” status.
>
> Dear Richard and Simon, Simon, Tom:
> You currently have “maybe”, “irrelevant” or “no” here. Do you indeed
> want to deviate from the documented plan of getting rid of
> NoMonadFailDesugaring?
>
> Cheers,
> Joachim
>
>
>
> --
> Joachim Breitner
>   mail at joachim-breitner.de
>   http://www.joachim-breitner.de/
>
>
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20201231/bdfbca94/attachment.html>