[ghc-steering-committee] [ghc-proposals/ghc-proposals] Lazy unboxed tuples / warn on unbanged strict patterns (#35)

[Simon Peyton Jones]

Colleagues

I didn’t think we had any 4-week discussion period.  I thought that it was up to the author to press the button, saying “I think the proposal is in its final form, and the community has had enough time to respond”.  At that point it moves from “Discussion” to “Committee decision” phase.


I guess there could be a minimum period: the author can’t press the button until the community really has had time.  But if they don’t want to push the button, fine.

I’m trying put the author in control as much as possible.

In decision mode we need a shepherd from the committee to push the discussion forward.  Ben, as our current secretary, should suggest who.

Incidentally the “proposals process” link in the opening sentence https://github.com/ghc-proposals/ghc-proposals leads back to the same page, which is unhelpful. It should lead to https://github.com/ghc-proposals/ghc-proposals/blob/master/proposal-submission.rst  (which is about the whole process, not just about submission despite the URL).

Simon

From: Ben Gamari [mailto:notifications at github.com]
Sent: 24 January 2017 04:35
To: ghc-proposals/ghc-proposals <ghc-proposals at noreply.github.com>
Cc: Simon Peyton Jones <simonpj at microsoft.com>; Comment <comment at noreply.github.com>
Subject: Re: [ghc-proposals/ghc-proposals] Lazy unboxed tuples / warn on unbanged strict patterns (#35)


Note that this proposal is now half-way through its four week discussion period. At the end of this period we ask @goldfirere<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoldfirere&data=02%7C01%7Csimonpj%40microsoft.com%7C2c56dc62d8de4944dc2408d444124e75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636208292805590167&sdata=JcitilvBwPvMmYiIpVVBRmjoXGO2ItnCv%2BrPy%2FsLitw%3D&reserved=0> to summarize the discussion and bring the proposal to the GHC committee for consideration. Thanks!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fpull%2F35%23issuecomment-274707495&data=02%7C01%7Csimonpj%40microsoft.com%7C2c56dc62d8de4944dc2408d444124e75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636208292805590167&sdata=Hg03Oek7o%2Bzl4j3S3koLw3CI7fI%2FjYpUUpn4ZWc2p0w%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAjsezzb1mOJxpcJRg8-90Aq3yyybLq_ks5rVX9cgaJpZM4Lfnkq&data=02%7C01%7Csimonpj%40microsoft.com%7C2c56dc62d8de4944dc2408d444124e75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636208292805590167&sdata=eHP3GYRrs5%2F8qfM8z%2BjEYU2JjaxPRDDJQCbMSTxRssU%3D&reserved=0>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20170125/3ab6fb6a/attachment.html>