- ghc-steering-committee

Please review #516: Introduce `-Wincomplete-record-selectors`, Shepherd: Eric
by Joachim Breitner 02 Oct '22

02 Oct '22

Dear Committee, Introduce `-Wincomplete-record-selectors` have been submitted by Adam Gundry https://github.com/ghc-proposals/ghc-proposals/pull/516 https://github.com/adamgundry/ghc-proposals/blob/incomplete-record-selector… I suggest that Eric shepherds 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/

6 10

Please review #518: Type vs Constraint proposal, Shepherd: Eric
by Joachim Breitner 02 Oct '22

02 Oct '22

Dear Committee, The Type vs Constraint proposal has been submitted by Richard Eisenberg and Simon Peyton Jones https://github.com/ghc-proposals/ghc-proposals/pull/518 https://github.com/ghc-proposals/ghc-proposals/blob/spj/type-vs-constraint/… I suggest that Eric shepherds 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/

5 10

Baldur stepping down
by Simon Peyton Jones 26 Sep '22

26 Sep '22

Friends I'm writing to let you know that Baldur (icelandjack) has decided to step down from the GHC Steering Committee. He is incredibly talented, but the commitments of his job and a newborn daughter (congratulations Baldur) have made it hard for him to keep up with GHC proposals. Thank you Baldur. You have given a lot to Haskell already (notably deriving via) and I'm sure there is lots more to come. best wishes Simon

1 0

Proposal #270: Support pun-free code. Recommendation: accept
by Chris Dornan 08 Sep '22

08 Sep '22

Hi all, I have been assigned to shepherd Proposal #270: Support pun-free code Proposal text: https://github.com/hithroc/ghc-proposals/blob/master/proposals/0000-support… Proposal discussion: https://github.com/ghc-proposals/ghc-proposals/pull/270 The proposal helps manage @data T = T@ style definitions that use the same name for type and data constructors. It introduces -Wpuns and -Wpun-bind to warn about puns at usage and binding sites, respectively, and adds qualified import syntax for importing selectively into the data and type name spaces: import Data.Proxy type qualified as T -- import only the type namespace import Data.Proxy data qualified as D -- import only the data namespace As the low number indicates the proposal has been around for a while and the author has an implementation PR: https://gitlab.haskell.org/ghc/ghc/-/merge_requests/2044. The most active discussion point was Simon’s observation that this extension introduces a ‘fork’ in the language: https://github.com/ghc-proposals/ghc-proposals/pull/270#issuecomment-536115…. (See Simon’s comment at the link for an explanation of the Haskell language fork idea.) There is a long tradition of using data/type constructor puns (older than Haskell itself) and many people will consider it good style (I certainly do), while others do not, and they will benefit from tools to help manage and limit their use. So, notwithstanding the fork-like nature of the proposal, because it is not very intrusive (some warnings with finer control of qualified imports), and it is helping folks to establish a subset that they are maintaining anyway, I am minded to accept this proposal — though it was close. My sole concern is that it could give rise to contentious pressure on the wider Haskell community to embrace the subset. To (avoiding) this end, I suggest that we include wording in the user guide section documenting this extension to the effect that there is no consensus on the desirability or otherwise of the punful code the extension seeks to address. Chris

5 17

Please review: #515 Relaxing HasField constraints
by Tom Harding 07 Sep '22

07 Sep '22

Hi all, Ollie Charles’ proposal <https://github.com/ghc-proposals/ghc-proposals/pull/515> removes the restrictions placed on HasField instances. Close to my heart, this addresses the problem of creating custom `HasField` instances for record types. I’m in favour of this proposal as it would solve some issues I have encountered, but the floor is open for discussion. Thanks, Tom

3 2

Please review #500: Add implicit import proposal, Shepherd: Baldur
by Joachim Breitner 05 Sep '22

05 Sep '22

Dear Committee, Add implicit import proposal has been submitted by Tristan de Cacqueray This is an interesting one: At first glance it looks quite un- haskellish, but it’s hard to poing out what’s, if anything, is wrong with it. I expect that the discussion will revolve not so much about technical issues, but more about best practices and our vision for Haskell’s look and feel. https://github.com/ghc-proposals/ghc-proposals/pull/500 https://github.com/TristanCacqueray/ghc-proposals/blob/implicit-import/prop… I suggest that Baldur, as our newest committee member, gets to shepherd this one. 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/

6 9

GHC Proposals session at Haskell Symposium at ICFP
by Joachim Breitner 30 Aug '22

30 Aug '22

Hello Committee and all else who follow this list, this year’s Haskell Symposium will host a special “GHC Proposals session” where current, future and past GHC Proposals can be presented and discussed: https://icfp22.sigplan.org/home/haskellsymp-2022#GHC-Proposals-Session I invite all GHC Proposal authors (or otherwise interested party) who are in Ljubljana to present your ideas and plans; just e-mail me if you want a slot. I also invite all committee members who are around to join, this is a great way to learn more about the proposals and have a real face-to- face discussion about them. (Committee members who also author proposals ideally do both :-)) I know this is rather short notice, but I still hope we can source some presentations and make this a productive meeting. Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Please review #532: Clean up implicit binding, Shepherd: Arnaud
by Joachim Breitner 23 Aug '22

23 Aug '22

Dear Committee, Clean up and simplify the treatment of implicit binding have been submitted by John Ericson https://github.com/ghc-proposals/ghc-proposals/pull/532 https://github.com/Ericson2314/ghc-proposals/blob/type-variables/proposals/… This is a refinement of Modern Scoped Type variables (#448), where John believe we have left some things undone. Hence I’d like to ask Arnaud to also shepherd this one. Note that John’s #532 actually makes edits to a few existing proposals (#425, #448, #523) to clean them up; the linked proposal above explains and summarizes the changes, but also note the full diff of the PR. 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/

1 0

GHC Steering Committee Status
by Joachim Breitner 19 Aug '22

19 Aug '22

Dear Committee, let’s do another bimonthly status update . It seems that the last two months were quite quiet on the mailing list, but we did get a bunch of new submissions. Time to get active again! So what has happened since the last one? * PSA: You make my life when preparing these reports easier if every state change comes with a (small) email to the list. In particular sending a proposal back for revision is often not noted on the list. * we were asked to review these proposals: #511 Deep Subsumption, Shephard: Arnaud #330 Decorate exceptions with backtrace information, Shepherd: Vladislav #518 Type vs Constraint proposal, Shepherd: Eric #515 Relaxing HasField constraints, Shepherd: Tom #517 Require implementors before proposal submission, Shepherd: Simon PJ #522 Or Patterns, Shepherd: Richard #516 Introduce `-Wincomplete-record-selectors`, Shepherd: Eric * I reassigned the following proposal #500: Add implicit import proposal, New Shepherd: Simon M. * we have a recommendation from the shepherd about: #518 Type vs Constraint proposal (accept) #517 Require implementors before proposal submission (accept) #515 Relaxing HasField constraints (accept) #511 Deep Subsumption (accept) * we have sent the following proposals back to revision #330 Decorate exceptions with backtrace information #473: First-class existential types #454: Custom type warnings * we decided about the following proposals #448 Modern Scoped Type Variables (accept) #518 Type vs Constraint proposal (accept) (merge still pending a ✓ from Richard) #496 Nothing {} (acccept) #511 Deep Subsumption (accept) We currently have to act on the following 6 proposals, same number as last time. ## Waiting for committee decision #515 Relaxing HasField constraints 2022-08-01: Assigned to Tom 2022-08-10: Tom suggests acceptance No comments so far. Please voice your opinions! #517: Require implementors before proposal submission, Shepherd Simon 2022-08-01: Assigned to Simon 2022-08-05: Simon suggests acceptance Only supporting comments so far. ## Waiting for Shepherd action #270: Support pun-free code, Shepherd: Chris 2022-01-01: Assigned to Chris Chris, kindly please leap into action! #500: Add implicit import proposal, Shepherd: Baldur 2022-05-05: Assignd to Baldur 2022-08-01: Re-assignd to Simon #522: Or Patterns 2022-08-08: Assigned to Richard #516: Introduce `-Wincomplete-record-selectors`, Shepherd: Eric 2022-08-14: Assigned to Eric Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

2 1

Please review #522: Or Patterns, Shepherd: Richard
by Joachim Breitner 09 Aug '22

09 Aug '22

Dear Committee, Or Patterns have been submitted by David Knothe, Ömer Sinan Ağacan, Sebastian Graf https://github.com/ghc-proposals/ghc-proposals/pull/522 https://github.com/knothed/ghc-proposals/blob/master/proposals/0522-or-patt… It even lists implementors, in what we’d call vorauseilender Gehorsam in German! I suggest that Richard shepherds 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/

1 0