November 2023 - ghc-steering-committee

#493: SPECIALISE with expressions, rec: accept
by Adam Gundry 22 Jan '24

22 Jan '24

Dear all, Richard and Simon propose to generalise SPECIALISE pragmas to allow expressions, not just type signatures: https://github.com/ghc-proposals/ghc-proposals/pull/493 https://github.com/goldfirere/ghc-proposals/blob/specialise/proposals/0000-… This does not add anything fundamentally new, because such SPECIALISE pragmas can be translated using the existing RULES machinery, but it does make several idioms substantially more convenient: * Using type applications in a SPECIALISE pragma to avoid repetition * Manual call-pattern specialisation * Loop unrolling Thus I propose we accept this proposal. 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 9

Please review #569: multiline string literals, Shepherd: Eric
by Joachim Breitner 01 Jan '24

01 Jan '24

Dear Committee, Brandon Chinn has a proposal for multiline string literals. Let the bikeshedding begin. https://github.com/ghc-proposals/ghc-proposals/pull/569 https://github.com/brandonchinn178/ghc-proposals/blob/multiline-strings/pro… I’d like to nominate Eric as the shepherd. 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/

4 6

GHC2024 committee deliberation
by Joachim Breitner 04 Dec '23

04 Dec '23

Dear Committee, I’d like to get the committe involvement in GHC2024 started. The current proposal is at https://github.com/ghc-proposals/ghc-proposals/pull/613 https://github.com/ghc-proposals/ghc-proposals/blob/joachim/ghc2024/proposa… At the moment, six changes relative to CHC2021 are proposed by committee and by community members. See the proposal for rationales. My goal is to have a decision in time for 9.10. I suggest we use November to deliberate the proposals and maybe add more changes to the list, and then vote in early December. We’ll put each change separately on the ballot. I know that there are ongoing discussions that could arguably affect how we want the next GHC20xx to look like, in particular the just opened #620, and I anticipate a desire to postpone GHC2024 until that has been decided. But I recall that we postponed GHC2023 for (among other reasons) for the same reason, and I wouldn’t be surprised that if in a year we have yet another unresolved question that seems worth waiting for. If this pattern reminds you of the GHC release process before we introduced the regular cadence, then maybe you’ll agree that if we want a predictable and reasonable frequent stream of language editions, we have to avoid such delays when feasible. So please let us know what you think of the proposed changes, what other changes you want to see, or if you have qualms about the process. Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

4 19

Please review #606: 281 to use atype instead of ktype, Shepherd: Richard
by Joachim Breitner 30 Nov '23

30 Nov '23

Dear Committee, Vladislav Zavialov proposes a grammar amendment to types in terms: https://github.com/ghc-proposals/ghc-proposals/pull/606 https://github.com/ghc-proposals/ghc-proposals/pull/606/files I’d like to nominate Richard as the shepherd. 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/

1 0

GHC stability discussions
by Simon Peyton Jones 09 Nov '23

09 Nov '23

Dear GHC Steering Committee We have several threads about GHC's stability in progress: - Proposal 601: GHC extension life cycle <https://github.com/david-christiansen/ghc-proposals/blob/extension-lifecycl…>. This introduces the notion of a "Stable" and "Experimental" extension. It was written by David C but has stalled now that he has stepped down as ED. - GHC Stability Goals <https://docs.google.com/document/d/1wtbAK6cUhiAmM6eHV5TLh8azEdNtsmGwm47Zulg…>, builds on #601 with general rules GR1-3. This is not a change to GHC (hence not a GHC proposal) more a clarification about how the GHC Steering Committee works. - Proposal 620: Extensions and warnings <https://github.com/ghc-proposals/ghc-proposals/blob/wip/spj-extensions-and-…>. This proposal keeps moving in the same direction, unifying warnings and extensions. - Proposal 617: add -experimental flag <https://github.com/ghc-proposals/ghc-proposals/pull/617>. This builds on #601 by providing an enforcement mechanism. It is strongly affected by #620. It would be good to get some of this decided. Too much is in the air at the moment! Personally I think: - We can agree at least the Stable/Experimental part of #601 - The Stability Goals seem fairly uncontroversial. Shall we just make it part of the GHC Proposal process documentation - #620 is new; your views would be welcome - The approach to #617 may depend on the outcome of #620. Simon

2 3