Re: [ghc-steering-committee] #195 recommendation: accept

when the details are eventually sorted out But when will that be? Our criteria say that the proposal should stand by itself before we finally accept it. If there are specifics that we think belong in the proposal, then our protocol is: * tell the authors that we are minded to accept, * invite them to fill in the missing stuff and resubmit * change status to “needs revision” I don’t think we should formally accept proposals that are ill-specified, in the hope that they’ll subsequently be fixed up. Pushing back to “please revise to address these points” is not a negative thing – it’s a positive thing, saying good proposal but let’s make it better. Simon From: Spiwack, Arnaud Sent: 06 November 2019 08:46 To: Richard Eisenberg Cc: Simon Peyton Jones ; ghc-steering-committee Subject: Re: [ghc-steering-committee] #195 recommendation: accept I understand that some details are lacking. But I don't think, whatever the details are, that they will affect my opinion of the proposal: they are over my knowledge of Template Haskell. This proposal seems well motivated. So, I'll count as an accept vote, when the details are eventually sorted out. On Tue, Nov 5, 2019 at 10:45 PM Richard Eisenberg mailto:rae@richarde.dev> wrote: I'm in the same camp as Simon here -- I'm still a little murky on how `Code` will interact with `Q`. Richard

On Nov 5, 2019, at 5:23 PM, Simon Peyton Jones via ghc-steering-committee mailto:ghc-steering-committee@haskell.org> wrote:

I'm basically supportive, but would like to see answers to my recent questions incorporated in the proposal before it is accepted. https://github.com/ghc-proposals/ghc-proposals/pull/195#issuecomment-5475225...https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fpull%2F195%23issuecomment-547522510&data=02%7C01%7Csimonpj%40microsoft.com%7C527240705f664101bba108d76295dabb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637086268899169898&sdata=n8uk%2Fnppc%2FjrfkQ31O9YTiEwenBgj%2FxZb70oFr4oX5M%3D&reserved=0

Simon

| -----Original Message----- | From: ghc-steering-committee mailto:ghc-steering-committee-bounces@haskell.org> | On Behalf Of Iavor Diatchki | Sent: 05 November 2019 16:44 | To: ghc-steering-committee mailto:ghc-steering-committee@haskell.org> | Subject: [ghc-steering-committee] #195 recommendation: accept | | Hello everyone, | | I am the shepherd for pull request #195 to wrap `Q (TExtp a)` into a | newtype synonym `Code a`. The main change to the language is that the | special Template Haskell notation for typed splices will will work | with `Code a` rather than `Q (TExtp a)`. | | The benefit of having the newtype is that it makes it possible to | abstract over `Code`. For example, you can work with typed name | environments like `MapF Name Code`, where `MapF` is an "indexed" | variant of `Map` which maps `Name a` to `Code a` (`MapF` is defined in | package `parameterized-utils` on hackage). | | Making typed TH work with `Code` directly avoids the need to | constantly switch between `Code` and `Q (TExp a)` and with the new | system users of typed TH are not likely to deal with the latter much | at all. | | For these reasons I recommend that we accept this proposal. Please | let me know if you think otherwise. | | -Iavor | _______________________________________________ | ghc-steering-committee mailing list | ghc-steering-committee@haskell.orgmailto:ghc-steering-committee@haskell.org | https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.has | kell.orghttps://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkell.org&data=02%7C01%7Csimonpj%40microsoft.com%7C527240705f664101bba108d76295dabb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637086268899169898&sdata=Hn9JTcGQkvhDnxdV%2FDQsDSB%2FsfzzQPKCQHXF3eItPmw%3D&reserved=0%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering- | committee&data=02%7C01%7Csimonpj%40microsoft.comhttps://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F40microsoft.com&data=02%7C01%7Csimonpj%40microsoft.com%7C527240705f664101bba108d76295dabb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637086268899179890&sdata=19DoeBZc06cv4N%2BU8ZP7%2FQJNsSku7Rfo902SPB1aBOY%3D&reserved=0%7Ce2fd3cfd09334b865fb | 308d7620f5a8c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637085690437517 | 136&sdata=Qug9nwlVpQIY2U6jw%2FXKOnPpNPfiG6EAfWgv%2BTOJ4e0%3D&reser | ved=0 _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.orgmailto:ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committeehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&data=02%7C01%7Csimonpj%40microsoft.com%7C527240705f664101bba108d76295dabb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637086268899189882&sdata=RB0VvVusRaa2rws1UZzuIg4TlM2gv42zPia3oNOO4T8%3D&reserved=0

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.orgmailto:ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committeehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&data=02%7C01%7Csimonpj%40microsoft.com%7C527240705f664101bba108d76295dabb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637086268899189882&sdata=RB0VvVusRaa2rws1UZzuIg4TlM2gv42zPia3oNOO4T8%3D&reserved=0