[ghc-steering-committee] Proposal #592: Scoped kind variables in standalone kind signatures (recommend accept)

Moritz Angermann moritz.angermann at gmail.com
Wed Feb 21 09:44:56 UTC 2024


I must admit this is a bit outside of my usual realm of Haskell. I trust
the more knowledgeable members of this group to have a more informed view
on this than I do.
>From the associated discussion on the ticket, I'm pleased to see that
breakage has been taken into consideration.

+1 from me.

On Tue, 20 Feb 2024 at 05:37, Eric Seidel <eric at seidel.io> wrote:

> All, I've only heard from SimonPJ, Arnaud, and Richard. Please voice your
> assent or dissent. Otherwise I will take silence as assent and accept the
> proposal this weekend.
>
> On Wed, Feb 14, 2024, at 15:33, Richard Eisenberg wrote:
> > Yes, looks good to me. This is a natural part of -XExtendedForAllScope.
> > Which, though I dislike, seems to be around for good (and admittedly is
> > quite convenient).
> >
> > On Tue, Feb 13, 2024 at 11:39 AM Arnaud Spiwack <arnaud.spiwack at tweag.io>
> wrote:
> >> I haven't taken time to check that the specification that Vlad wrote is
> the same as that of -XExtendedForAllScope for type signatures and function
> definitions. But I trust that Vlad did his homework.
> >>
> >> This makes perfect sense to me, though I'm not sure this is worth
> spending time on, considering that we seem to be going in the direction to
> deprecate -XExtendedForAllScope.
> >>
> >> On Mon, 12 Feb 2024 at 23:39, Simon Peyton Jones <
> simon.peytonjones at gmail.com> wrote:
> >>> I support this too.
> >>>
> >>> Simon
> >>>
> >>> On Sat, 10 Feb 2024 at 03:10, Eric Seidel <eric at seidel.io> wrote:
> >>>> Dear Committee,
> >>>>
> >>>> Vlad has found what looks like a clear gap in the interaction between
> >>>> two extensions: -XStandaloneKindSignatures and -XExtendedForAllScope.
> >>>>
> >>>> I think it's quite obvious that under -XExtendedForAllScope the forall
> >>>> in a standalone kind signature should behave like the forall in a
> >>>> standalone type signature, i.e. it should scope over the definition
> >>>> as well.
> >>>>
> >>>> I recommend accepting this amendment to StandaloneKindSignatures.
> >>>>
> >>>> Eric
> >>>>
> >>>> https://github.com/ghc-proposals/ghc-proposals/pull/592
> >>>>
> https://github.com/int-index/ghc-proposals/blob/scoped-saks/proposals/0054-kind-signatures.rst#proposed-change-specification
> >>>> _______________________________________________
> >>>> ghc-steering-committee mailing list
> >>>> ghc-steering-committee at haskell.org
> >>>>
> 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
> >>
> >>
> >> --
> >> Arnaud Spiwack
> >> Director, Research at https://moduscreate.com and https://tweag.io.
> >> _______________________________________________
> >> ghc-steering-committee mailing list
> >> ghc-steering-committee at haskell.org
> >>
> 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
> _______________________________________________
> 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/20240221/f2e648f3/attachment.html>


More information about the ghc-steering-committee mailing list