[ghc-steering-committee] Status
Tom Harding
i.am.tom.harding at gmail.com
Fri Jan 15 11:11:30 UTC 2021
Apparently so! Apologies for falling behind; I haven’t got into the swing of 2021 yet 😄
I will make sure to get caught up with everything today!
Thanks,
Tom
> On 14 Jan 2021, at 16:27, Simon Peyton Jones via ghc-steering-committee <ghc-steering-committee at haskell.org> wrote:
>
> | In addition to the two meta-proposals (bylaws and GHC2021), we currently
> | have to act on the following 7 proposals, up by 2!
> | Some need some nudging.
>
> Tom, I think you offered to be our nudger. Do you need nudging 😊?
>
> Simon
>
>
> | -----Original Message-----
> | From: ghc-steering-committee <ghc-steering-committee-bounces at haskell.org>
> | On Behalf Of Joachim Breitner
> | Sent: 13 January 2021 22:14
> | To: ghc-steering-committee at haskell.org
> | Subject: [ghc-steering-committee] Status
> |
> | Dear Committee,
> |
> | after 2½ months, time for a new status updates. What was going on here?
> |
> | * Well, GHC2021 was going on. Lots of it. But it’s actually coming to a
> | close
> | in five days. It will be exciting to see how it affects the Haskell
> | landscapes.
> |
> | * Heh, last status I wrote:
> |
> | Richard refines the bylaws in #360. Maybe everybody has a second
> | look now and then we can merge this?
> |
> | I guess that still applies. Richard and I are discussing a corner case
> | on the PR, but otherwise approvals are coming in, and unless that
> | changes,
> | we’ll merge that once we ironed out that wrinkle.
> |
> | * Simon introduced the position of a nudger, namely Tom.
> |
> | Tom, below are some PRs where you might need to nudge someone!
> |
> | * we were asked to review these proposals:
> | #366: DuplicateRecordFields without ambiguous field access, shepherd:
> | Tom
> | #242: Unsaturated type families, Shepherd: Richard Eisenberg
> | #370: Syntax for Modifiers, Shepherd: Alejandro
> | #387: The Char kind, Shepherd: Alejandro
> | #368: Warn on prefix/suffix operators, Shepherd: Tom
> | #381: Visible 'forall' in types of terms, Shepherd: Iavor
> |
> | * we have a recommendation from the shepherd about:
> | #369: Add sumToTag# primop, (rec: accept)
> | #366: DuplicateRecordFields without ambiguous field access (rec:
> | accept)
> | #381: Visible 'forall' in types of terms (rec: reject)
> | #242: Unsaturated type families (rec: accept)
> | #313: Delimited continuation primops (rec: accept)
> | #370: Syntax for Modifiers (rec: accept)
> | #387: The Char kind (rec: accept)
> |
> | * we have sent the following proposals back to revision
> | #283: Local modules
> |
> | * we decided about the following proposals
> | #366: DuplicateRecordFields without ambiguous field access (accept)
> | #370: Syntax for Modifiers (accept)
> | #242: Unsaturated type families (accept)
> |
> | In addition to the two meta-proposals (bylaws and GHC2021), we currently
> | have to act on the following 7 proposals, up by 2!
> | Some need some nudging.
> |
> | ## Waiting for committee decision
> |
> | #387: The Char kind, Shepherd: Alejandro
> | Looks like it’ll be smoothly accepted, but it’s only a week old.
> | Will maybe merge in a few days.
> |
> | #381: Visible 'forall' in types of terms, Shepherd: Iavor
> | Recommendation was to reject, but discussion went into the more
> | abstract “whither dependent Haskell”. But what does this mean
> | for this proposal?
> |
> | #369: Add sumToTag# primop
> | Essentially accepted, waiting for feedback from the author on final
> | tweaks
> |
> | #313: Delimited continuation primops, Shepherd: Simon Marlow
> | Mostly positive reception, but there was discussion.
> | Simon, can this be accepted as it, or does it need more
> | work/time/discussion?
> |
> | #302: \of, Shepherd: Cale
> | No new discussion. Cale, what is the conclusion?
> |
> |
> | ## Waiting for Shepherd action
> |
> | #367: Clarify primops using unboxed sums, Shepherd: Simon Marlow
> | This is aging… we need a shepherd recommendation
> |
> | #368: Warn on prefix/suffix operators, Shepherd: Tom
> | Tom, your turn
> |
> | Cheers,
> | Joachim
> | --
> | Joachim Breitner
> | mail at joachim-breitner.de
> |
> | https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.joach
> | im-
> | breitner.de%2F&data=04%7C01%7Csimonpj%40microsoft.com%7Cf129a6d1884e49
> | 46c9a308d8b8109e51%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6374617288
> | 40678377%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> | iI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6kMsahaFt6ayhXgbN11R7c5cATDzN9X
> | iqLJg0Mo5saE%3D&reserved=0
> |
> |
> | _______________________________________________
> | ghc-steering-committee mailing list
> | ghc-steering-committee at haskell.org
> | https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.has
> | kell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-
> | committee&data=04%7C01%7Csimonpj%40microsoft.com%7Cf129a6d1884e4946c9a
> | 308d8b8109e51%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637461728840688
> | 372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik
> | 1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TSiM7uiX06Ux3Gj98pUIbzNuebrnK6FMESmr
> | bMCpGio%3D&reserved=0
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
More information about the ghc-steering-committee
mailing list