November 2019 - ghc-steering-committee

Please review #285: -XNoImplicitForAll, Shepherd: Simon Marlow
by Joachim Breitner 04 May '20

04 May '20

Dear Committee, this is your secretary speaking: -XNoImplicitForAll has been proposed by John Ericson https://github.com/ghc-proposals/ghc-proposals/pull/285 https://github.com/Ericson2314/ghc-proposals/blob/no-implicit-forall/propos… I propose Simon Marlow as the shepherd. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

5 9

Please review #265: Unlifted Datatypes, Shepherd: Simon Marlow
by Joachim Breitner 30 Jan '20

30 Jan '20

Dear Committee, this is your secretary speaking: Unlifed Datatypes has been proposed by Sebastian Graf https://github.com/ghc-proposals/ghc-proposals/pull/265 https://github.com/sgraf812/ghc-proposals/blob/unlifted-data/proposals/0000… I propose Simon Marlow as the shepherd, as the expert on low-level stuff. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

6 11

Please review #282: RecordDotSyntax, Shepherd: Simon PJ
by Joachim Breitner 28 Nov '19

28 Nov '19

Dear Committee, this is your secretary speaking: RecordDotSyntax language extension proposal has been proposed by Neil Mitchell and Shayne Fletcher https://github.com/ghc-proposals/ghc-proposals/pull/282 https://github.com/shayne-fletcher-da/ghc-proposals/blob/record-dot-syntax/… This is going to be a tricky one. It is partly about whitespace, so it has attracted a _lot_ of community interest, by far the most so far. To navigate that ship, I propose Simon PJ as the shepherd, because he is a excellent moderator and community manager, and because he has the necessary authority to hopefully get a verdict accepted. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Managing github notifications?
by Sandy Maguire 26 Nov '19

26 Nov '19

Hi all, I'm wondering if anyone has a good strategy for dealing with github noise. Right now I feel like I need to choose between silence and overwhelming volume, and neither is good for me to do my job on this committee. I'd like to be informed when someone opens a new proposal PR in order to read it, but not for any of the follow-up commentary. As best I can tell, there is no github option that allows for this. Any advice on this would be greatly appreciated. Thanks, Sandy -- I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! https://isovector.github.io/erdos/

3 2

Please review #273: Local Types, Shepherd: Eric
by Joachim Breitner 26 Nov '19

26 Nov '19

Dear Committee, this is your secretary speaking: Local Types has been updated by David Feuer https://github.com/ghc-proposals/ghc-proposals/pull/273 https://github.com/treeowl/ghc-proposals/blob/local-types/proposals/0000-lo… I propose Eric as the shepherd. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

5 7

Updated partial type signatures (#194) - recommendation: accept
by Vitaly Bragilevsky 25 Nov '19

25 Nov '19

Hi everyone, Being the shepherd to the Updated partial type signatures proposal (#194, https://github.com/ghc-proposals/ghc-proposals/pull/194) I recommend acceptance. I've posted the rationale behind this recommendation on Github thread ( https://github.com/ghc-proposals/ghc-proposals/pull/194#issuecomment-554751… ). In short: the proposal unifies the treatment of underscores and identifiers beginning with underscores everywhere outside patterns. It also brings more control to partial type signatures. Please, raise your voices here or there. As usual, silence is understood as an agreement. Vitaly

4 3

Please review #246: Overloaded Quotations, Shepherd: Simon PJ
by Joachim Breitner 22 Nov '19

22 Nov '19

Dear Committee, this is your secretary speaking: Overloaded Quotations has been proposed by Matthew Pickering https://github.com/ghc-proposals/ghc-proposals/pull/246 https://github.com/mpickering/ghc-proposals/blob/overloaded-proposal/propos… I propose Simon PJ as the shepherd, as it seems he already had some in depth discussion about this proposal. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

8 8

Amendment #293; recommendation: accept
by Richard Eisenberg 20 Nov '19

20 Nov '19

3 2

#195 recommendation: accept
by Iavor Diatchki 15 Nov '19

15 Nov '19

Hello everyone, I am the shepherd for pull request #195 to wrap `Q (TExtp a)` into a newtype synonym `Code a`. The main change to the language is that the special Template Haskell notation for typed splices will will work with `Code a` rather than `Q (TExtp a)`. The benefit of having the newtype is that it makes it possible to abstract over `Code`. For example, you can work with typed name environments like `MapF Name Code`, where `MapF` is an "indexed" variant of `Map` which maps `Name a` to `Code a` (`MapF` is defined in package `parameterized-utils` on hackage). Making typed TH work with `Code` directly avoids the need to constantly switch between `Code` and `Q (TExp a)` and with the new system users of typed TH are not likely to deal with the latter much at all. For these reasons I recommend that we accept this proposal. Please let me know if you think otherwise. -Iavor

5 13

Please review again #177: Simple constrained type families, Shepherd: Richard
by Joachim Breitner 05 Nov '19

05 Nov '19

Dear Committee, this is your secretary speaking: Simple constrained type families has been revised by Alexis Williams https://github.com/ghc-proposals/ghc-proposals/pull/117 https://github.com/typedrat/ghc-proposals/blob/constrained-type-families/pr… I propose Richard as the Shepherd. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

2 1