- ghc-steering-committee

Please review #496: Nothing {}, Shepherd: Eric
by Joachim Breitner 29 Jun '22

29 Jun '22

Dear Committee, Empty records with {} have been proposed by John Ericsson https://github.com/ghc-proposals/ghc-proposals/pull/496 https://github.com/Ericson2314/ghc-proposals/blob/empty-record-wildcards/pr… This seems to be about straightening a corner case, so to say. I suggest Eric as the shepherd. 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 6

Please review: #454 Custom type warnings
by Tom Harding 25 Jun '22

25 Jun '22

Hi all, As Joachim noted, #454 <https://github.com/ghc-proposals/ghc-proposals/pull/454> is extracted from Adam’s previous efforts with the Unsatisfiable constraint <https://github.com/ghc-proposals/ghc-proposals/pull/433> proposal (which has since been accepted). In short, it covers an interface for custom warnings, and I can already think of plenty of ways I’d use it. I’d therefore like to recommend acceptance, and discuss any issues or changes. Thanks, Tom

6 9

GHC Steering Committee Status
by Joachim Breitner 13 Jun '22

13 Jun '22

Dear Committee, it’s about time for my ~monthly~ ~quarterly~ bimonthly status update So what has happened since the last one? * I proposed that we proposals upon submission ought to have some indication that there is someone willing and able to implement it, please join the discussion on https://github.com/ghc-proposals/ghc-proposals/pull/517 * we were asked to review these proposals: #500: Add implicit import proposal, Shepherd: Baldur #473: First-class existential types, Shepherd: Simon PJ #496: Nothing {}, Shepherd: Eric * we have a recommendation from the shepherd about: #496: Nothing {}, rec: accept * we have sent the following proposals back to revision none, it seems * we decided about the following proposals #451: Sized literals proposal (accept) We currently have to act on the following 6 proposals, up 2 since last update: ## Waiting for committee decision #454: Custom type warnings, Shepherd: Tom 2022-01-13: Recommendation to accept 2022-06-01: Arnaud says objections are minor. Tom, do you think we have consensus here? #448: Modern Scoped Type Variables, Shepherd: Arnaud 2022-03-29: Arnaud makes a non-comprehensive recommendation 2022-06-07: Ongoing discussion #496: Nothing {}, Shepherd: Eric 2022-06-12: Eric suggests acceptance ## 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 #473: First-class existential types, Shepherd: Simon PJ 2022-05-16: Assigned to Simon Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

2 2

Please review #473: First-class existential types, Shepherd: Simon PJ
by Joachim Breitner 07 Jun '22

07 Jun '22

Dear Committee, First-class existential types has been submitted by Richard https://github.com/ghc-proposals/ghc-proposals/pull/374 https://github.com/goldfirere/ghc-proposals/blob/existentials/proposals/047… Exciting stuff! This feels, at least to me, like a proposal with major implications – not least because I believe it means that type equality will now involve some form of term equivalence, and may thus affect what kind of Core transformations are still type-preserving. Therefore I would suggest Simon PJ 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/

2 1

Any future plans for HasField redesign?
by John Walker 12 May '22

12 May '22

Hello Committee, I was wondering if there are any near to middle term plans to move forward with hasField redesign which I believe is an enabler for setter with record dot syntax. The ticket ( https://gitlab.haskell.org/ghc/ghc/-/merge_requests/3257) has a milestone of 9.4.1 and it looks like the proposal is done ( https://github.com/adamgundry/ghc-proposals/blob/hasfield-redesign/proposal…) pending feedback some time ago but hasn't got to discussions yet ( https://github.com/ghc-proposals/ghc-proposals/pull/0) thanks John

2 1

Please review #451: Sized literals proposal; Shepherd: Simon M
by Richard Eisenberg 23 Apr '22

23 Apr '22

Dear Committee, This is your interim secretary speaking: Sized literals proposal, proposing syntax for literals for the new sized primitive numeric types, has been proposed by Sylvain Henry. https://github.com/ghc-proposals/ghc-proposals/pull/451 https://github.com/hsyl20/ghc-proposals/blob/sized-literals/proposals/0000-… I propose Simon M as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Thanks, Richard

4 4

GHC Steering Committee Status
by Joachim Breitner 07 Apr '22

07 Apr '22

Dear Committee, it’s about time for my ~monthly~ quarterly status update So what has happened since the last one? * We decided 7 proposals since then. That’s pretty good! * Simon suggested a better way to keep tabs on what’s going on, and you’ll find the second half of this mail at https://github.com/ghc-proposals/ghc-proposals/wiki/Status As before, I still didn’t get around to mess with markdown tables etc… Maybe I just don’t feel the itch enough. * Membership changes! Alejandro has stepped down, Vitaly rotated out and Baldur and Chris joined. Bladur and Chris, you have been quite quiet here so far. Make yourself heard! * we were asked to review these proposals: #454: Custom type warnings (shepherd: Tom) #448: Modern Scoped Type Variables (shepherd: Arnaud) #270: Support pun-free code (resubmission; shepherd: Vitaly, later Chris) #475: New tuple and list syntax (resubmission; shepherd: Vlad) #277: Unicode ellipsis (shepherd: Joachim) * we have a recommendation from the shepherd about: #460: migration plan for non-magical-~ (rec: accept) #451: sized literals (rec: accept) #454: Custom type warnings (rec: accept) #475: New tuple and list syntax (rec: accept) #277: Unicode ellipsis (rec: accept) #425: invisible binders in type decls (rec: accept) #448: Modern Scoped Type Variables (rec: mostly accept) * we have sent the following proposals back to revision none, it seems * we decided about the following proposals #319: NoFallibleDo (reject) #392: Clarify modifiers design principle (accept) #460: migration plan for non-magical-~ (accept) #475: New tuple and list syntax (accept) #277: Unicode ellipsis (accept) #452: Articulate principles for GHC evolution (accept) #425: invisible binders in type declarations (accept) We currently have to act on the following 4 proposals, down by 2 since last update: ## Waiting for committee decision #451: Sized Literals, Shepherd: Simon M. 2022-01-11: Recommendation to accept by Simon Simon asked the committee for the color of the shed! Please all weigh in! #454: Custom type warnings, Shepherd: Tom 2022-01-13: Recommendation to accept There was contention (by Vlad) if the possible performance impact is too bad, with a bit of active discussion on Github #448: Modern Scoped Type Variables, Shepherd: Arnaud 2022-03-29: Arnaud makes a non-comprehensive recommendation Ongoing discussion about which parts should be accepted and which not (yet). Thanks Arnaud, for guiding the discussion. ## Waiting for Shepherd action #270: Support pun-free code, Shepherd: Chris 2022-01-01: Assigned to Chris Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

#425: invisible binders in type declarations; rec: accept
by Richard Eisenberg 07 Apr '22

07 Apr '22

Hi all, I am the shepherd for proposal #425, https://github.com/ghc-proposals/ghc-proposals/pull/425, proposing to add invisible binders in type declarations. The main payload of the proposal is to allow definitions like > data Proxy @k (a :: k) = Proxy instead of today's > data Proxy (a :: k) = Proxy which has no explicit binding site for k. This new syntax solves a number of smallish syntax conundra, as very well outlined in the proposal. In addition, the proposal includes two small unrelated tweaks to the syntax of type family instances; these are points (6) and (7) in the proposal. Both changes will break some obscure (but still realistic, knowing Haskell) programs, but both fixes are backward compatible. --- I recommend acceptance. The proposal is motivated nicely (do check out the examples) and solves a real problem. The new syntax fits in with other similar features. The small cleanups to existing syntax will lead to better error messages. The one drawback, as I see it, is that this proposal includes point (5), which is a breaking change to the way type synonyms work. Right now, we can say > type P = (Proxy :: k -> Type) and GHC will infer P :: forall k. k -> Type. Under this proposal, you would have to write > type P @k = (Proxy :: k -> Type) bringing k into scope explicitly. The fix is not backward compatible, and so I think this proposal should come with a migration strategy, where we warn about the former version for some releases before banning it. (Continuing to support it is possible, but it's very awkward to have a variable mentioned only in a synonym's right-hand side.) Sorry for the delay in producing this recommendation! Richard

5 8

Please review #270: Support pun-free code, Shepherd: Chris Dornan
by Joachim Breitner 01 Apr '22

01 Apr '22

Dear Committee, Support pun-free code has been resubmitted (again) by Artyom Kuznetsov https://github.com/ghc-proposals/ghc-proposals/pull/270 https://github.com/hithroc/ghc-proposals/blob/master/proposals/0000-support… This was previously shepherded by Iavor, and then shepherded by Vitaly. I hope it’s not poisonous. I suggest that Chris takes over. 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

#477: Unicode ellipsis, recommendation: accept
by Joachim Breitner 30 Mar '22

30 Mar '22

Dear Committee, Proposal #277 “Unicode ellipsis” has been submitted by Ignat Insarov, and I’m shepherding it myself. https://github.com/ghc-proposals/ghc-proposals/pull/477 https://github.com/kindaro/ghc-proposals/blob/unicode-ellipsis/proposals/47… This is a very small proposal that lets GHC understand the nice Unicode syntax `…` in places where in ASCII world we have .., under -XUnicodeSyntax. I am fond of Unicode in general, and I expect that users of - XUnicodeSyntax expect this to work, and therefore recommend acceptance of this proposal. Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

7 14