
Dear Committee, another “regular” status update. So what has happened in the last two months? * Lots of discussion about GHC2020. Enough to make it rather GHC2021. * Richard refines the bylaws in #360. Maybe everybody has a second look now and then we can merge this? * we were asked to review these proposals: #356: Linear Types arrow, shepherd: Richard #351: NoIncomplete, shepherd: Iavor #364: Unify Nat and Natural, shepherd: Alejandro #283: Local modules, Shepherd: Arnaud #367: Clarify primops using unboxed sums, Shepherd: Simon Marlow #369: Add sumToTag# primop, Shepherd: Eric * we have a recommendation from the shepherd about: #302: \of (rec: reject) #356: Linear Types arrow (rec: vote) #364: Unify Nat and Natural (rec: accept) #281: Visible 'forall' in types of terms (rec: accept) #283: Local modules (rec: accept) * we have sent the following proposals back to revision #281: Visible 'forall' in types of terms * we decided about the following proposals #356: Linear Types arrow (accept) #364: Unify Nat and Natural (accept) We currently have to act on the following 5 proposals, up by 3. ## Waiting for committee decision #313: Delimited continuation primops, Shepherd: Simon Marlow #367: Clarify primops using unboxed sums, Shepherd: Simon Marlow ## Waiting for Shepherd action #333: Defer Parse Errors, Shepherd: Tom Tom, is this ready for Committee consideration? #302: Layout and Guards in Lambda Expressions, Shepherd: Cale Cale, it is high time to jump into action here! Cheers, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/

On #281 I initially recommended acceptance, but after the discussion I
realized that I haven't fully understood all the implications of the
proposal, and some tricky issues came up, so we changed the status to
"needs revision". After a short period of time, the author asked me to
resubmit the proposal again, but there appears to be a bunch of discussion
still happening, so I am waiting for things to calm down again, before I
read it again, and see what's changed.
I have some deadlines coming up, so I won't be able to deal with committee
stuff until about mid next week---apologies for that, hopefully nothing is
particularly urgent.
-Iavor
On Tue, Oct 27, 2020 at 11:02 AM Joachim Breitner
Dear Committee,
another “regular” status update. So what has happened in the last two months?
* Lots of discussion about GHC2020. Enough to make it rather GHC2021.
* Richard refines the bylaws in #360. Maybe everybody has a second look now and then we can merge this?
* we were asked to review these proposals: #356: Linear Types arrow, shepherd: Richard #351: NoIncomplete, shepherd: Iavor #364: Unify Nat and Natural, shepherd: Alejandro #283: Local modules, Shepherd: Arnaud #367: Clarify primops using unboxed sums, Shepherd: Simon Marlow #369: Add sumToTag# primop, Shepherd: Eric
* we have a recommendation from the shepherd about: #302: \of (rec: reject) #356: Linear Types arrow (rec: vote) #364: Unify Nat and Natural (rec: accept) #281: Visible 'forall' in types of terms (rec: accept) #283: Local modules (rec: accept)
* we have sent the following proposals back to revision #281: Visible 'forall' in types of terms
* we decided about the following proposals #356: Linear Types arrow (accept) #364: Unify Nat and Natural (accept)
We currently have to act on the following 5 proposals, up by 3.
## Waiting for committee decision
#313: Delimited continuation primops, Shepherd: Simon Marlow
#367: Clarify primops using unboxed sums, Shepherd: Simon Marlow
## Waiting for Shepherd action
#333: Defer Parse Errors, Shepherd: Tom Tom, is this ready for Committee consideration?
#302: Layout and Guards in Lambda Expressions, Shepherd: Cale Cale, it is high time to jump into action here!
Cheers, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

After a short period of time, the author asked me to resubmit the proposal again, but there appears to be a bunch of discussion still happening, so I am waiting for things to calm down again, before I read it again, and see what's changed.
You might want to let the author know. Committee discussion is a bit stalled until you give a recommendation.
Alternatively you could be asking us to express an opinion about the proposal in its current state?
I’m just conscious that no proposal should sit in the committee’s bailiwick for long.
Simon
From: ghc-steering-committee

I did let them know on github. Also the proposal was resubmitted to the
committee only 4 days ago, so we are within the stated limits.
Also, I'd encourage members of the committee interested in the proposal to
continue the discussion, and not feel blocked by me.
-Iavor
On Tue, Oct 27, 2020 at 1:27 PM Simon Peyton Jones
After a short period of time, the author asked me to resubmit the proposal again, but there appears to be a bunch of discussion still happening, so I am waiting for things to calm down again, before I read it again, and see what's changed.
You might want to let the author know. Committee discussion is a bit stalled until you give a recommendation.
Alternatively you could be asking us to express an opinion about the proposal in its current state?
I’m just conscious that no proposal should sit in the committee’s bailiwick for long.
Simon
*From:* ghc-steering-committee
*On Behalf Of *Iavor Diatchki *Sent:* 27 October 2020 18:26 *To:* Joachim Breitner *Cc:* ghc-steering-committee *Subject:* Re: [ghc-steering-committee] Status On #281 I initially recommended acceptance, but after the discussion I realized that I haven't fully understood all the implications of the proposal, and some tricky issues came up, so we changed the status to "needs revision". After a short period of time, the author asked me to resubmit the proposal again, but there appears to be a bunch of discussion still happening, so I am waiting for things to calm down again, before I read it again, and see what's changed.
I have some deadlines coming up, so I won't be able to deal with committee stuff until about mid next week---apologies for that, hopefully nothing is particularly urgent.
-Iavor
On Tue, Oct 27, 2020 at 11:02 AM Joachim Breitner < mail@joachim-breitner.de> wrote:
Dear Committee,
another “regular” status update. So what has happened in the last two months?
* Lots of discussion about GHC2020. Enough to make it rather GHC2021.
* Richard refines the bylaws in #360. Maybe everybody has a second look now and then we can merge this?
* we were asked to review these proposals: #356: Linear Types arrow, shepherd: Richard #351: NoIncomplete, shepherd: Iavor #364: Unify Nat and Natural, shepherd: Alejandro #283: Local modules, Shepherd: Arnaud #367: Clarify primops using unboxed sums, Shepherd: Simon Marlow #369: Add sumToTag# primop, Shepherd: Eric
* we have a recommendation from the shepherd about: #302: \of (rec: reject) #356: Linear Types arrow (rec: vote) #364: Unify Nat and Natural (rec: accept) #281: Visible 'forall' in types of terms (rec: accept) #283: Local modules (rec: accept)
* we have sent the following proposals back to revision #281: Visible 'forall' in types of terms
* we decided about the following proposals #356: Linear Types arrow (accept) #364: Unify Nat and Natural (accept)
We currently have to act on the following 5 proposals, up by 3.
## Waiting for committee decision
#313: Delimited continuation primops, Shepherd: Simon Marlow
#367: Clarify primops using unboxed sums, Shepherd: Simon Marlow
## Waiting for Shepherd action
#333: Defer Parse Errors, Shepherd: Tom Tom, is this ready for Committee consideration?
#302: Layout and Guards in Lambda Expressions, Shepherd: Cale Cale, it is high time to jump into action here!
Cheers, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/ https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.joachim-breitner.de%2F&data=04%7C01%7Csimonpj%40microsoft.com%7Cb09bb398b6994336807d08d87aa5d390%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637394199923776422%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=wRy1%2FGf7IgAYhHOMuod7JofjCZbNeFwiqsK34Cny5fU%3D&reserved=0
_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&data=04%7C01%7Csimonpj%40microsoft.com%7Cb09bb398b6994336807d08d87aa5d390%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637394199923776422%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=MfQeAmjPtAiv92jI8hK%2BbiocmWnt%2FTYILVT1TMnKF9I%3D&reserved=0
participants (3)
-
Iavor Diatchki
-
Joachim Breitner
-
Simon Peyton Jones