- ghc-steering-committee

Status
by Joachim Breitner 20 Feb '18

20 Feb '18

Cheers everyone, Since the last status update, we * were asked to review these proposals: - Int8#/Word8# - unlifted newtypes - plugin recompilation API * got a recommendation from shepherds about: - incomplete-uni-patterns (accept) - embrace Type in Type (recommendation is somewhat unclear) - Deprecate STM invariant (accept) - Unlifted newtypes (accept) - mutable constructor fields (accept) - plugin recompilation API (accept) * decided about the following proposals - Or patterns (sent back for refinement) - Deprecate STM invariant (accept) - incomplete-uni-patterns (accept) Good job, team! On our table at the moment are 7 proposals: Mutable constructor fields https://github.com/ghc-proposals/ghc-proposals/pull/8 Shepherd: Ryan Newton Status: Ryan recommends acceptance Lazy unboxed tuples https://github.com/ghc-proposals/ghc-proposals/pull/35 Shepherd: Ryan Newton Status: Waiting for Ryan to make a recommendation. Visible dependent quantification (TL;DR: forall k -> k -> *) https://github.com/ghc-proposals/ghc-proposals/pull/81 Shepherd: Roman Leshchinskiy Status: Discussion ebbed down. Do we have consensus? Embrace (Type :: Type) https://github.com/ghc-proposals/ghc-proposals/pull/83 Shepherd: Iavor Diatchki Status: Iavor started a discussion Small primitive types https://github.com/ghc-proposals/ghc-proposals/pull/74 Shepherd: Simon Marlow Status: Waiting for Simon to make a recommenataion Unlifted Newtypes https://github.com/ghc-proposals/ghc-proposals/pull/98 Shepherd: Richard Eisenberg Status: Richard recommends acceptance Plugin recompilation avoidance https://github.com/ghc-proposals/ghc-proposals/pull/108 Shepherd: Ben Gamari Status: Ben suggests acceptance, but I am nitpicking Besides these, there are some proposals actively under discussion. You can always check them out at https://github.com/ghc-proposals/ghc-proposals/pulls?q=is%3Aopen+is%3Apr+no… Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Please review: plugin recompilation avoidance, Shepherd: Ben Gamari
by Joachim Breitner 14 Feb '18

14 Feb '18

Dear Committee, this is your secretary speaking: An API for deciding whether plugins should cause recompilation was proposed: https://github.com/ghc-proposals/ghc-proposals/pull/108 I propose Ben Gamari as the Shepherd. Ben, please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

2 1

Do we consider the GHC API in scope?
by Joachim Breitner 13 Feb '18

13 Feb '18

Hi, in https://github.com/ghc-proposals/ghc-proposals/pull/108 David proposed changes to the plugin API. The propsosal is still under discussion (so if you want to comment, do it there), but more generally, I wonder: Is the GHC API (including the one for plugins) in scope for the GHC steering committee? Or should they go the same route as other, genuinely internal changes in GHC, which would be Trac and Phab? Note that plugins often have to import arbitrary GHC modules, not just GhcPlugins, so really every exported function in GHC is part of the GHC API and hence the plugin API? Cheers, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

5 7

Please review: unlifted newtypes, Shepherd: Richard Eisenberg
by Joachim Breitner 11 Feb '18

11 Feb '18

Dear Committee, this is your secretary speaking: Unlifted Newtypes were proposed https://github.com/ghc-proposals/ghc-proposals/pull/98 I propose Richard Eisenberg as the Shepherd. Richard, please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

2 1

Please review: embrace Type::Type, Shepherd: Iavor
by Joachim Breitner 11 Feb '18

11 Feb '18

Dear Committee, this is your secretary speaking: Richards proposes to merge -XTypeInType into -XPolyKinds and -XDataKinds https://github.com/ghc-proposals/ghc-proposals/pull/83 I propose Yavor Diatchki as the Shepherd. Yavor, please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

3 2

Proposal: accept "add incomplete-uni-patterns and incomplete-record-updates to -Wall"
by Simon Marlow 08 Feb '18

08 Feb '18

I propose that we accept the proposal add incomplete-uni-patterns and incomplete-record-updates to -Wall https://github.com/ghc-proposals/ghc-proposals/pull/71 <https://github.com/ghc-proposals/ghc-proposals/pull/71> Both warnings are avoidable and considered bad style, which makes them appropriate to include in -Wall. The reason that -Wincomplete-uni-patterns wasn't originally made part of -Wall was due to worries about noisiness ( https://ghc.haskell.org/trac/ghc/ticket/4905) but that's not a valid concern. -Wall is intentionally a moving target, if you want to stay Wall-clean you accept that new compiler releases may entail some work. Basically I think this is a no-brainer. Cheers Simon

5 4

Proposal #77 "Deprecating STM invariant mechanism" — suggesting acceptance
by Manuel M T Chakravarty 03 Feb '18

03 Feb '18

Folks, I’d like to reach consensus on Proposal #77 ”Deprecating STM invariant mechanism”: https://github.com/bgamari/ghc-proposals/blob/deprecate-stm-invariants/prop… (The discussion thread is at <https://github.com/ghc-proposals/ghc-proposals/pull/77>.) This proposal is about removing a rarely used feature that is arguably buggy and also imposes significant complexity. I think, removing ideas that turn out to be not working properly or simply aren’t sufficiently useful for the complexity they impose is an important part of the process. The STM invariant mechanism appears to fit that bill. Hence, I suggest to accept this proposal. Please let me know if you disagree; otherwise, I will assume tacit approval. Cheers, Manuel

4 3

Deadlines for Shepherds?
by Joachim Breitner 08 Jan '18

08 Jan '18

Hi, you know that I like slim smooth processes with not too many rules, and our current process worked pretty nicely for the first few proposals. But now it seems that we lost some steam, and a fair number of proposals are stuck waiting for their Shepherd to make progress. Does this mean that people simply need deadlines for work to be done? Do you want deadlines? Also, I am happy to re-assign some stalled proposals to new shepherds. Does anyone want to volunteer recommending a decision for one or more of these proposals: Lazy unboxed tuples https://github.com/ghc-proposals/ghc-proposals/pull/35 Mutable constructor fields https://github.com/ghc-proposals/ghc-proposals/pull/8 Deprecate STM invariant mechanism https://github.com/ghc-proposals/ghc-proposals/pull/77 -Wall to include incomplete-uni-patterns and incomplete-record-updates https://github.com/ghc-proposals/ghc-proposals/pull/71 Thanks, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

4 3

Status
by Joachim Breitner 06 Jan '18

06 Jan '18

Dear Committee, welcome to the new year 2018. Since the last status update, we * were asked to review these proposals: - merge -XTypeInType * accepted the following proposals: - /none/ * sent the following proposals back for further refinement - /none/ * rejected the following proposals: - /none/ On our table at the moment are: Lazy unboxed tuples https://github.com/ghc-proposals/ghc-proposals/pull/35 Shepherd: Ryan Newton Status: Still waiting for Ryan to make a recommendation. Mutable constructor fields https://github.com/ghc-proposals/ghc-proposals/pull/8 Shepherd: Ryan Newton Status: Still waiting for Ryan to make a recommendation. Or Patterns https://github.com/ghc-proposals/ghc-proposals/pull/43 Shepherd: Manuel Chakravarty Status: Committee deliberation ongoing, likely expecting changes. Visible dependent quantification (TL;DR: forall k -> k -> *) https://github.com/ghc-proposals/ghc-proposals/pull/81 Shepherd: Roman Leshchinskiy Status: Roman suggested changes, a slow discussion is happening. Deprecate STM invariant mechanism https://github.com/ghc-proposals/ghc-proposals/pull/77 Shepherd: Manuel Chakravarty Status: Waiting for Manuel to make a recommendation -Wall to include incomplete-uni-patterns and incomplete-record-updates https://github.com/ghc-proposals/ghc-proposals/pull/71 Shepherd: Simon Marlow Status: Waiting for Simon to make a recommendation Embrace (Type :: Type) https://github.com/ghc-proposals/ghc-proposals/pull/83 Shepherd: Iavor Diatchki Status: Waiting for Iavor to make a recommendation Besides these, there are some proposals actively under discussion. You can always check them out at https://github.com/ghc-proposals/ghc-proposals/pulls?q=is%3Aopen+is%3Apr+no… Greetings, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0

Status
by Joachim Breitner 06 Dec '17

06 Dec '17

Dear Commmittteee, Since the last status update, we * were asked to review these proposals: - visible dependent quantification - Deprecate STM invariant mechanism - add incomplete-uni-patterns and incomplete-record-updates to -Wall - Block arguments * accepted the following proposals: - underscores in literals - Block arguments * sent the following proposals back for further refinement - /none/ * rejected the following proposals: - /none/ * Had a discussion how to scale the committee process to “big” proposals like linear types. On our table at the moment are: Lazy unboxed tuples https://github.com/ghc-proposals/ghc-proposals/pull/35 Shepherd: Ryan Newton Status: Still waiting for Ryan to make a recommendation. Mutable constructor fields https://github.com/ghc-proposals/ghc-proposals/pull/8 Shepherd: Ryan Newton Status: Still waiting for Ryan to make a recommendation. Or Patterns https://github.com/ghc-proposals/ghc-proposals/pull/43 Shepherd: Manuel Chakravarty Status: Manuel suggests acceptance, committee deliberation ongoing Visible dependent quantification (TL;DR: forall k -> k -> *) https://github.com/ghc-proposals/ghc-proposals/pull/81 Shepherd: Roman Leshchinskiy Status: Waiting for Roman to make a recommendation Deprecate STM invariant mechanism https://github.com/ghc-proposals/ghc-proposals/pull/77 Shepherd: Manuel Chakravarty Status: Waiting for Manuel to make a recommendation -Wall to include incomplete-uni-patterns and incomplete-record-updates https://github.com/ghc-proposals/ghc-proposals/pull/71 Shepherd: Simon Marlow Status: Waiting for Simon to make a recommendation Dear shepherds, there is work waiting for you! Besides these, there are some proposals actively under discussion. You can always check them out at https://github.com/ghc-proposals/ghc-proposals/pulls?q=is%3Aopen+is%3Apr+no… Greetings, Joachim -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0