[ghc-steering-committee] GHC Steering Comittee Status

[Joachim Breitner]

Dear Committee,

an easterly status update. The last 1½ was relatively active, and we
have a solit throughput. Keep it up!

So here’s the delta since last month.

 * Vladislav joined!

   Also Iavor, Richard and me re-joined.

 * we were asked to review these proposals:
   #405: Split RecordDotSyntax, Shepherd: Simon PJ
   #403: lexical structure of numbers and identifiers, Shepherd: Arnaud
   #400: Constrained COMPLETE sets, Shepherd: Cale
   #402: Stable GADT constructor syntax, Shepherd: Richard
   #378: Support ergonomic dependent types, Shepherd: Simon PJ
   #283: Local modules, Shepherd: Arnaud
   #396: Defaulting plugins, Shepherd: Vladislav
   #371: Stop treating ~ magically, Shepherd: Richard
   #409: Exportable named defaults, Shepherd: Eric

 * we have a recommendation from the shepherd about:
   #390: Fine-grained pragmas, recommendation: accept
   #405: Split RecordDotSyntax, rec: accept
   #403: Cleanup lexical structure, recommendation: accept
   #367: Clarify primops using unboxed sums, rec: reject
   #402: Changes to GADT syntax; rec: accept
   #378: support the design for dependent types, rec: accept
   #371: Stop treating ~ magically. rec: weak accept

 * we have sent the following proposals back to revision
   #381: Visible 'forall' in types of terms
   #302: \of
   #390: Fine-grained pragmas

 * we decided about the following proposals
   #369: Add sumToTag# (accept)
   #403: Cleanup lexical structure (accept)
   #367: Clarify primops using unboxed sums (reject)
   #405: Split RecordDotSyntax (accept)
   #403: Cleanup lexical structure (accept)

We currently have to act on the following 6 proposals, up by 1.

## Waiting for committee decision

#402: Stable GADT constructor syntax, Shepherd: Richard
      Recommendation is to accept. There is some ongoing discussion if
      extra parents should be continued to be allowed.

#371: Stop treating ~ magically, Shepherd: Richard
      Recommendation is to accept. Some ongoing discussion
      about whether exporting ~ might be pragmatic choice.

#378: Support ergonomic dependent types, Shepherd: Simon PJ
      Recommendation is to accept, but there are some doubts
      that this is a proper proposal that should be addressed
      first. I expect some more soul-searching here.

## Waiting for Shepherd action

#283: Local modules, Shepherd: Arnaud
      Waiting for recommendation.

#400: Constrained COMPLETE sets, Shepherd: Cale
      Waiting for recommendation.

#409: Exportable named defaults, Shepherd: Eric
      Waiting for recommendation.


Cheers,
Joachim
-- 
Joachim Breitner
  mail at joachim-breitner.de
  http://www.joachim-breitner.de/