[ghc-steering-committee] Please review #259: No kind signatures on associated types Shepherd: Simon PJ

[Simon Peyton Jones]

All,

I'm the shepherd for

|  No kind signatures on associated types
|  https://github.com/ghc-proposals/ghc-proposals/pull/259

I recommend acceptance.

The proposal takes the form of an amendment to an earlier accepted proposal
   Standalone kind signatures
   https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0054-kind-signatures.rst

by prohibiting a standalone kind signature for the associated type of a class.

The reason for this narrowing is well described in the "Associated types" subsection of the revised proposal.

The first link above lets you see the baseline proposal, the diff, and the new proposal.

I recommend acceptance because
- the need for standalone signatures on
  associated types is weaker (albeit not absent)
- allowing such a signature closes of one possible
  future direction

So making them illegal now keeps our options open for the future.

Since standalone kind signatures are not yet released, there will be no back-compat issues.

Please express your opinion.  I don't think this one is controversial.

Simon


|  -----Original Message-----
|  From: ghc-steering-committee <ghc-steering-committee-bounces at haskell.org>
|  On Behalf Of Joachim Breitner
|  Sent: 05 September 2019 09:43
|  To: ghc-steering-committee at haskell.org
|  Subject: [ghc-steering-committee] Please review #259: No kind signatures
|  on associated types Shepherd: Simon PJ
|  
|  Dear Committee,
|  
|  this is your secretary speaking:
|  
|  No kind signatures on associated types
|  has been proposed by Richard
|  https://github.com/ghc-proposals/ghc-proposals/pull/259
|  
|  I propose Simon PJ as the shepherd, this seems to be a smaller fix of an
|  existing proposal and Simon has already looked at it.
|  
|  Please reach consensus as described in
|  https://github.com/ghc-proposals/ghc-proposals#committee-process
|  In particular, talk to the authors before, if you think this should be
|  rejected, and kick off the discussion on Github, following the steps
|  described under “Now the shepherd proposes to accept or reject the
|  proposal” in the above link.
|  
|  Thanks,
|  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