- ghc-steering-committee

Please review #536: Type-level literals as a separate language extension, Shepherd: Vlad
by Joachim Breitner 06 Mar '23

06 Mar '23

Dear Committee, Ross Paterson proposes Type-level literals as a separate language extension https://github.com/ghc-proposals/ghc-proposals/pull/536 https://github.com/RossPaterson/ghc-proposals/blob/literals/proposals/0000-… I suggest Vlad to shepherd this, as he has already engaged with it on Github. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

3 2

Please review #512: NoFieldSelectors as datatype annotation, Shepherd: Baldur
by Joachim Breitner 02 Mar '23

02 Mar '23

Dear Committee, NoFieldSelectors as datatype annotation have been proposed by Matt Parsons https://github.com/ghc-proposals/ghc-proposals/pull/512 https://github.com/parsonsmatt/ghc-proposals/blob/matt/field-selectors-scop… I suggest Baldur to shepherd this proposal. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

9 29

Call for votes: Shall we have GHC2023
by Joachim Breitner 10 Feb '23

10 Feb '23

Hi Committee, as ~threatened~ announced, I’m calling for a vote on whether we should proceed to define the next GHC20xx _now_, as GHC2023, or wait for a year. Judging from the silence around the PR for GHC2023 I deduce that the appetite for GHC2023 is generally low, and will not bother you with complicated looking questions about which extensions might make GHC2023 worth it in an attempt to parallelize the “whether” with the “what”. Instead, please cast your vote until Apri 5 (but preferrably earlier) on the question: Should we proceed towards GHC2023? (If yay wins we’ll refine #559 and vote on that. If nay wins, I’ll stay quiet until next fall.) I am intentionally not asking for a fixed cadence at this point. We have made but one release so far, and it seems presumptious to try to predict what makes most sense next year, or the next four years to come. (I’ll follow up with my vote and justification separately.) Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

7 11

Proposal #556 recommendation: accept
by Richard Eisenberg 09 Feb '23

09 Feb '23

Hi all, Vlad has proposed https://github.com/ghc-proposals/ghc-proposals/pull/556, an amendment to recently accepted proposal #448 on scoped type variables. It adds a nuance saying that f (MkT @(a :: <<here>>)) = ... should have the same scoping behavior as f (MkT (x :: <<here>>)) = ... Note that the first is a kind signature of a visible-type-application-in-a-pattern, while the second is a pattern signature. The intended scoping rule says that the use of an in-scope type variable in these positions is an occurrence, while the use of an out-of-scope type variable brings that variable into scope. Vlad's proposal corrects the phrasing in the original proposal that aligns the treatment of the kind signature with the type it is describing, forbidding e.g. the use of a repeated variable in the kind signature. Vlad's amendment makes the proposal what I had intended when I wrote #448; I strongly recommend acceptance. I think this is a small tweak of a technical detail buried in #448 and hope this does not cause widespread debate. I will accept this proposal in a week if I don't hear objections. Thanks! Richard

4 4

#515 Relaxing HasField constraints, reassigned to Moritz
by Joachim Breitner 09 Feb '23

09 Feb '23

Hi committee, with Tom stepping down, we have to re-assign this proposal: #515 Relaxing HasField constraints https://github.com/ghc-proposals/ghc-proposals/pull/515 https://github.com/ocharles/ghc-proposals/blob/hasfield/proposals/0000-hasf… It was submitted in August 2022, and Tom recommended acceptance. Richard raised technical issues with it. I’d like to assign it to Adam, but he’s a co-author… So in best tradition of our committee, I’ll assign this to Moritz. Moritz, can you help drive the discussion, here and/or on Github? Maybe the proposal needs to be revised, based on Richard’s objections? Then you can label it as “needs-revision” until the authors come back to you. Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Thanks, Tom!
by Joachim Breitner 09 Feb '23

09 Feb '23

Hi, Tom told me that it’s time for him to step down. Thanks, Tom, for your service on the committee in the last three years, and don’t be a stranger to GHC! (Tom was an “expiring member” anyways since January, but we are still 10 members strong, so this does not trigger a new call for nominations. The next regular call for nomination will happen next spring when Richard’s, Vlad’s and my terms expire.) Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Welcome Moritz Angermann
by Joachim Breitner 08 Feb '23

08 Feb '23

Hello everybody, the committee welcomes Moritz Angermann as our newest member! Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

3 2

Fast tracked amendment: Warning category syntax (#576)
by Joachim Breitner 05 Feb '23

05 Feb '23

Hi, implementation work on warning categories (#541) shows that the implementation would be much simpler if the category was lexed as a string literal, and Adam wants to amend his warning category proposal to the syntax {-# WARNING in "x-some-category" "message" #-} This amendment is at https://github.com/ghc-proposals/ghc-proposals/pull/576. This seems to be changing a minor aspect of the original proposal and implementation is ready, so I think we can fast-track accepting this. If you disagree with this process please complain until the end of the week (Sun Feb 5). Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

2 2

Fast tracked amendment: No #. label (#573)
by Joachim Breitner 05 Feb '23

05 Feb '23

Hi, implementation work on #170 led to insights that called for small adjustments to the design, namely to remove dot from characters allowed in overloaded labels. The proposal is amended at https://github.com/ghc-proposals/ghc-proposals/pull/573. This should be part of 9.6, so I’d like to fast-track this for acceptance. If you disagree with this process please complain until the end of the week (Sun Feb 5). Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

3 3

By-law change: Allow self-nominations
by Joachim Breitner 05 Feb '23

05 Feb '23

Hi, our current by-law kinda bind our hands in case some motivated comes along and would like to join the committee, and Simon PJ suggested that we should give us the discretion to hold membership votes out-of-season as well. The suggested wording change is in https://github.com/ghc-proposals/ghc-proposals/pull/572 Please discuss and cast your vote within two weeks (preferably earlier, as you can guess this change is not happening completely out of the blue.) I’m in favor. Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

4 4