[ghc-steering-committee] CUSKs and StandaloneTypeSignatures

[Richard Eisenberg]

I think StandaloneKindSignatures should be included. It's true that there may be implementation bugs, but the design of them is really quite straightforward, so I don't expect design bugs. And I think it's design bugs that should hinder inclusion, much more than implementation bugs (of which I know none, at the moment).

Richard

> On Dec 4, 2020, at 9:15 AM, Spiwack, Arnaud <arnaud.spiwack at tweag.io> wrote:
> 
> CUSKs need to go. I see no place for them in the defaults.
> 
> I want StandaloneKindSignature in the default too, but I think that they are not battle-tested enough to be included this time around.
> 
> On Fri, Dec 4, 2020 at 2:45 PM Alejandro Serrano Mena <trupill at gmail.com <mailto:trupill at gmail.com>> wrote:
> Maybe some part of this discussion got lost.
> 
> Simon PJ writes:
> 
> Let's *not* have CUSKs.  We are trying to get rid of it... it'd be deeply strange to "bless" it in GHC2020.
> 
> StandaloneKindSignatures is clearly the Right Thing. I'm sure we'll want it long term.  
> 
> It's a very graceful fit with PolyKinds.
> 
> 
> I would really like StandaloneTypeSignatures to be part of the default, and remove CUSKs. Thoughts on this? Is it too early?
> 
> Regards,
> Alejandro
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org <mailto:ghc-steering-committee at haskell.org>
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee <https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee>
> _______________________________________________
> 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/20201204/45b747c9/attachment.html>