- ghc-steering-committee

Nudger
by Simon Marlow 21 Oct '25

21 Oct '25

While perusing the GHC Steering Committee Bylaws <https://github.com/ghc-proposals/ghc-proposals/blob/master/committee.rst> I noticed they mention that one committee member is dedicated the "Nudger". This is a role we introduced back in 2020 as far as I can make out; the nudger at the time was Tom Harding who is no longer a committee member. I don't think we appointed a new nudger when Tom left the committee. We should either 1. Abandon the idea and remove the text about the Nudger from the bylaws, or 2. Appoint a new nudger. I don't feel strongly, but lean towards (1). We tried it, it worked so well that we all forgot about it entirely :) Cheers Simon

2 2

Call for a volunteer to run a new nominations round
by Adam Gundry 15 Oct '25

15 Oct '25

Dear Committee, Arnaud and I are now approaching the end of our current three-year terms on the committee, which means the committee needs to put out a new public call for membership nominations. Our bylaws explain the process in more detail (https://github.com/ghc-proposals/ghc-proposals/blob/ master/committee.rst#term-limits-and-committee-selection). In particular, note that: > Expiring members are free to re-nominate themselves. When the > secretary's term is expiring, another (unexpiring) member of the > committee fills in for the secretary to run this process ... It is > expected that the committee favor newcomers in preference to re- > nominated continuing members. Since my term is expiring, I need to ask for a volunteer to run the nomination process (i.e. receive self-nominations from interested parties, distribute them to the other committee members and tally votes). Please speak up ASAP if you're willing to take this on! Thanks, Adam -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England

2 1

Qualified *
by Erik de Castro Lopo 15 Oct '25

15 Oct '25

Dear Committee, The original Qualified Literals proposal [1] has been split into 3 separate proposals: * Qualfied Strings [2] * Qualified Numerics [3] * Qualified Lists [4] Since this proposal has already been open for so long and had so much discussion, I have recommened that the committee reaches a decision by Oct 7. I had a few minor reservations about Numerics and Lists, mainly about the fact that there are still options on how they would be implemented but have recommended all 3 are accepted. Thanks, Erik [1] https://github.com/ghc-proposals/ghc-proposals/pull/698 [2] https://github.com/ghc-proposals/ghc-proposals/pull/723 [3] https://github.com/ghc-proposals/ghc-proposals/pull/724 [4] https://github.com/ghc-proposals/ghc-proposals/pull/725 -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

10 14

Qualified literals
by Simon Peyton Jones 17 Sep '25

17 Sep '25

Dear Simon, Jakob, Malte, Moritz, Matthias As you will know, there has been quite a bit of discussion around the GHC proposal for Qualified Literals. But (unless I have missed your contributions) you have not yet contributed to the discussion. As a member of the GHC Steering Committee, especially when there are tricky judgement calls to make (as in this case) I would really appreciate your input. - Discussion <https://github.com/ghc-proposals/ghc-proposals/pull/698> - Proposal <https://github.com/brandonchinn178/ghc-proposals/blob/qualified-strings/pro…> Brandon has now split his proposal into three. I have outlined options in this comment <https://github.com/ghc-proposals/ghc-proposals/pull/698#issuecomment-326958…> . I feel that we owe the proposer some guidance on the way forward, and we can only do that if we all pay attention, rather than leaving it to Sebastian. (Thanks Sebastian!) thank you! Simon

8 10

Please review #681: Updates to modifiers proposal
by Adam Gundry 10 Sep '25

10 Sep '25

Dear Committee, Phil Hazelden proposes to amend the Modifiers proposal based on experience with the implementation: https://github.com/ghc-proposals/ghc-proposals/pull/681 I'd like to nominate Matthías as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals/blob/master/README.rst#commi…. If possible, please aim to make a recommendation by 23rd September 2025. Cheers, Adam -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England

1 0

Please review #698: Qualified Literals
by Adam Gundry 08 Sep '25

08 Sep '25

Dear Committee, Brandon Chinn proposes to introduce new extensions for qualified number, string and list literals: https://github.com/ghc-proposals/ghc-proposals/pull/698 https://github.com/brandonchinn178/ghc-proposals/blob/qualified-literals/pr… I'd like to nominate Erik as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals/blob/master/README.rst#commi… (thanks Sebastian for pointing out the previously broken link) Cheers, Adam -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England

6 12

Proposal process refinements, removal of Markdown option
by Adam Gundry 15 Aug '25

15 Aug '25

Hi everyone, There is some discussion going on around refining the proposal process documentation in this PR from VitWW: https://github.com/ghc-proposals/ghc-proposals/pull/712 https://github.com/VitWW/ghc-proposals/blob/update-readme/README.rst I'm not planning to send this PR through the full review process itself, but I wanted to flag it up in case anyone from the committee wishes to comment. One point in particular to note is the removal of Markdown format as an option for authors, so that all proposals will be ReStructuredText. It seems this was agreed in principle several years ago, but not subsequently implemented, per this discussion: https://github.com/ghc-proposals/ghc-proposals/issues/560 If anyone objects to this change, please do speak up. Cheers, Adam -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England

1 0

#705: Explicit Level Imports: refine specification for exports, recommendation: accept
by Arnaud Spiwack 13 Aug '25

13 Aug '25

Dear all, Matthew and team propose a very short revision of their accepted proposal for explicit level imports (this proposal, if you don't remember, is about being more precise, when importing modules, whether they need to be available to emit code, or also for Template Haskell, for better recompilation avoidance and cross-compilation support). I say revision, but really, this simply specifies some corner cases which, admittedly, were ambiguous with the original wording of the proposal. There's nothing controversial about it. We should accept very quickly. I'll be on holiday the next couple of weeks, so I won't be able to act on this for a while. I don't think it's worth waiting two weeks though. So Adam, unless someone complains, probably accept it at the end of next week. Best, Arnaud -- Arnaud Spiwack Director, Research at https://moduscreate.com and https://tweag.io.

3 3

Please review #669: Initial categorization of language extensions
by Adam Gundry 08 Aug '25

08 Aug '25

Dear Committee, Trevis Elser proposes a classification of (some) language extensions based on previous work in proposal #601 establishing categories: https://github.com/ghc-proposals/ghc-proposals/pull/669 https://github.com/telser/ghc-proposals/blob/initial-extension-categorizati… I'd like to nominate Malte Ott as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Cheers, Adam -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England

7 8

Please review #705: Refine Explicit Level Imports specification for exports
by Adam Gundry 24 Jul '25

24 Jul '25

Dear Committee, Matthew Pickering proposes to refine the specification for Explicit Level Imports (#682) to clarify the behaviour of module exports: https://github.com/ghc-proposals/ghc-proposals/pull/705 I'd like to nominate Arnaud as the shepherd, since he shepherded the original proposal. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals/blob/master/README.rst#commi… If possible it would be good to get a quick decision on this so the implementation can be sorted for 9.14. Cheers, Adam -- Adam Gundry, Haskell Consultant Well-Typed LLP, https://www.well-typed.com/ Registered in England & Wales, OC335890 27 Old Gloucester Street, London WC1N 3AX, England

1 0