Hi, never having done much with TH, I usually refrain from commenting on TH-related proposals. But I found the motivation of the proposal, and the solution when viewed from a certain altitude, convincing. I’ll comment there with a quick question why the alternative is bad. Cheers, Joachim Am Samstag, den 16.11.2019, 10:26 +0000 schrieb Simon Peyton Jones via ghc-steering-committee:

Dear Committee

For this proposal:

Overloaded Quotations has been proposed by Matthew Pickering https://github.com/ghc-proposals/ghc-proposals/pull/246 https://github.com/mpickering/ghc-proposals/blob/overloaded-proposal/proposa...

I propose that we accept. As you'll see in the discussion thread I have asked Matthew to clarify some issues, but I'd like to get a sense of the committee because I don't want him to invest a lot of effort if it'll be wasted.

But I think it all seems like a useful generalisation. It accommodates what we do, and allows us to do more. This will make a modest difference for some, but a very big difference for a few. As far as I can tell, it will -- at worst -- require a bit of API generalisation for some users, but perhaps not many, so it scores well on the back-compat front.

Opinions please. I rather dislike "silence as assent" because it allow us to dodge our responsibility to read proposals and form an opinion. So please express an opinion, even if you want to qualify it by saying you are no expert. Please try to do this within a week, and definitely no more than two.

It's also fine to point to bits of the proposal that you did not understand or found hard going. The proposal will only become stronger if it is better presented.

Add technical questions on the Github thread, and evaluative judgements here on the mailing list.

Thanks

Simon

...

-----Original Message----- From: ghc-steering-committee On Behalf Of Joachim Breitner Sent: 14 November 2019 13:50 To: ghc-steering-committee@haskell.org Subject: [ghc-steering-committee] Please review #246: Overloaded Quotations, Shepherd: Simon PJ

Dear Committee,

this is your secretary speaking:

Overloaded Quotations has been proposed by Matthew Pickering https://github.com/ghc-proposals/ghc-proposals/pull/246 https://github.com/mpickering/ghc-proposals/blob/overloaded- proposal/proposals/0000-overloaded-bracket.rst

I propose Simon PJ as the shepherd, as it seems he already had some in depth discussion about this proposal.

Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you.

Thanks, 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 -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/

I'm strongly in support. On Mon, Nov 18, 2019 at 1:21 AM Eric Seidel wrote:

I found both parts of the motivation compelling. I'm in support.

...

Hi,

never having done much with TH, I usually refrain from commenting on TH-related proposals. But I found the motivation of the proposal, and the solution when viewed from a certain altitude, convincing.

I’ll comment there with a quick question why the alternative is bad.

Cheers, Joachim

Am Samstag, den 16.11.2019, 10:26 +0000 schrieb Simon Peyton Jones via ghc-steering-committee:

...

Dear Committee

For this proposal:

Overloaded Quotations has been proposed by Matthew Pickering https://github.com/ghc-proposals/ghc-proposals/pull/246

https://github.com/mpickering/ghc-proposals/blob/overloaded-proposal/proposa...

...

I propose that we accept. As you'll see in the discussion thread I

have asked Matthew to clarify some issues, but I'd like to get a sense of

On Sat, Nov 16, 2019, at 06:35, Joachim Breitner wrote: the committee because I don't want him to invest a lot of effort if it'll be wasted.

...

...

But I think it all seems like a useful generalisation. It

accommodates what we do, and allows us to do more. This will make a modest difference for some, but a very big difference for a few. As far as I can tell, it will -- at worst -- require a bit of API generalisation for some users, but perhaps not many, so it scores well on the back-compat front.

...

Opinions please. I rather dislike "silence as assent" because it

allow us to dodge our responsibility to read proposals and form an opinion. So please express an opinion, even if you want to qualify it by saying you are no expert. Please try to do this within a week, and definitely no more than two.

...

It's also fine to point to bits of the proposal that you did not

understand or found hard going. The proposal will only become stronger if it is better presented.

...

Add technical questions on the Github thread, and evaluative

judgements here on the mailing list.

...

Thanks

Simon

...

-----Original Message----- From: ghc-steering-committee <

ghc-steering-committee-bounces@haskell.org>

...

...

On Behalf Of Joachim Breitner Sent: 14 November 2019 13:50 To: ghc-steering-committee@haskell.org Subject: [ghc-steering-committee] Please review #246: Overloaded Quotations, Shepherd: Simon PJ

Dear Committee,

this is your secretary speaking:

Overloaded Quotations has been proposed by Matthew Pickering https://github.com/ghc-proposals/ghc-proposals/pull/246 https://github.com/mpickering/ghc-proposals/blob/overloaded- proposal/proposals/0000-overloaded-bracket.rst

I propose Simon PJ as the shepherd, as it seems he already had some in depth discussion about this proposal.

Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you.

Thanks, 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 -- 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

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

-- I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! https://isovector.github.io/erdos/

Yes -- I support. Richard

On Nov 18, 2019, at 8:09 AM, Simon Marlow wrote:

Seems like a good idea to me. I support it.

On Sat, 16 Nov 2019 at 10:26, Simon Peyton Jones via ghc-steering-committee mailto:ghc-steering-committee@haskell.org> wrote: Dear Committee

For this proposal:

Overloaded Quotations has been proposed by Matthew Pickering https://github.com/ghc-proposals/ghc-proposals/pull/246 https://github.com/ghc-proposals/ghc-proposals/pull/246 https://github.com/mpickering/ghc-proposals/blob/overloaded-proposal/proposa... https://github.com/mpickering/ghc-proposals/blob/overloaded-proposal/proposa...

I propose that we accept. As you'll see in the discussion thread I have asked Matthew to clarify some issues, but I'd like to get a sense of the committee because I don't want him to invest a lot of effort if it'll be wasted.

But I think it all seems like a useful generalisation. It accommodates what we do, and allows us to do more. This will make a modest difference for some, but a very big difference for a few. As far as I can tell, it will -- at worst -- require a bit of API generalisation for some users, but perhaps not many, so it scores well on the back-compat front.

Opinions please. I rather dislike "silence as assent" because it allow us to dodge our responsibility to read proposals and form an opinion. So please express an opinion, even if you want to qualify it by saying you are no expert. Please try to do this within a week, and definitely no more than two.

It's also fine to point to bits of the proposal that you did not understand or found hard going. The proposal will only become stronger if it is better presented.

Add technical questions on the Github thread, and evaluative judgements here on the mailing list.

Thanks

Simon

| -----Original Message----- | From: ghc-steering-committee mailto:ghc-steering-committee-bounces@haskell.org> | On Behalf Of Joachim Breitner | Sent: 14 November 2019 13:50 | To: ghc-steering-committee@haskell.org mailto:ghc-steering-committee@haskell.org | Subject: [ghc-steering-committee] Please review #246: Overloaded | Quotations, Shepherd: Simon PJ | | Dear Committee, | | this is your secretary speaking: | | Overloaded Quotations | has been proposed by Matthew Pickering | https://github.com/ghc-proposals/ghc-proposals/pull/246 https://github.com/ghc-proposals/ghc-proposals/pull/246 | https://github.com/mpickering/ghc-proposals/blob/overloaded- https://github.com/mpickering/ghc-proposals/blob/overloaded- | proposal/proposals/0000-overloaded-bracket.rst | | I propose Simon PJ as the shepherd, as it seems he already had some in | depth discussion about this proposal. | | Please reach consensus as described in | https://github.com/ghc-proposals/ghc-proposals#committee-process https://github.com/ghc-proposals/ghc-proposals#committee-process | I suggest you make a recommendation, in a new e-mail thread with the | proposal number in the subject, about the decision, maybe point out | debatable points, and assume that anyone who stays quiet agrees with you. | | Thanks, | Joachim | -- | Joachim Breitner | mail@joachim-breitner.de mailto:mail@joachim-breitner.de | http://www.joachim-breitner.de/ http://www.joachim-breitner.de/

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org mailto:ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

Hello, In general I think this is a good idea. However, in its current form this proposal clashes with #195, at least if we intend to also apply it to typed TH. The issue is that `Code a` is not `Applicative`, because we cannot define `pure` for all Haskell types. I wonder if the full power of `Applicative` is actually needed to do the translation though? If not, perhaps we should modify `Quote` to reflect the operations that we need. -Iavor On Mon, Nov 18, 2019 at 11:27 PM Spiwack, Arnaud wrote:

I don't know much of Template Haskell, but from my standpoint, it looks like an API improvement. The costs appear to be minimal. So I support too.

On Mon, Nov 18, 2019 at 11:52 PM Richard Eisenberg wrote:

...

Yes -- I support.

Richard

On Nov 18, 2019, at 8:09 AM, Simon Marlow wrote:

Seems like a good idea to me. I support it.

On Sat, 16 Nov 2019 at 10:26, Simon Peyton Jones via ghc-steering-committee wrote:

...

Dear Committee

For this proposal:

Overloaded Quotations has been proposed by Matthew Pickering https://github.com/ghc-proposals/ghc-proposals/pull/246 https://github.com/mpickering/ghc-proposals/blob/overloaded-proposal/proposa...

I propose that we accept. As you'll see in the discussion thread I have asked Matthew to clarify some issues, but I'd like to get a sense of the committee because I don't want him to invest a lot of effort if it'll be wasted.

But I think it all seems like a useful generalisation. It accommodates what we do, and allows us to do more. This will make a modest difference for some, but a very big difference for a few. As far as I can tell, it will -- at worst -- require a bit of API generalisation for some users, but perhaps not many, so it scores well on the back-compat front.

Opinions please. I rather dislike "silence as assent" because it allow us to dodge our responsibility to read proposals and form an opinion. So please express an opinion, even if you want to qualify it by saying you are no expert. Please try to do this within a week, and definitely no more than two.

It's also fine to point to bits of the proposal that you did not understand or found hard going. The proposal will only become stronger if it is better presented.

Add technical questions on the Github thread, and evaluative judgements here on the mailing list.

Thanks

Simon

| -----Original Message----- | From: ghc-steering-committee | On Behalf Of Joachim Breitner | Sent: 14 November 2019 13:50 | To: ghc-steering-committee@haskell.org | Subject: [ghc-steering-committee] Please review #246: Overloaded | Quotations, Shepherd: Simon PJ | | Dear Committee, | | this is your secretary speaking: | | Overloaded Quotations | has been proposed by Matthew Pickering | https://github.com/ghc-proposals/ghc-proposals/pull/246 | https://github.com/mpickering/ghc-proposals/blob/overloaded- | proposal/proposals/0000-overloaded-bracket.rst | | I propose Simon PJ as the shepherd, as it seems he already had some in | depth discussion about this proposal. | | Please reach consensus as described in | https://github.com/ghc-proposals/ghc-proposals#committee-process | I suggest you make a recommendation, in a new e-mail thread with the | proposal number in the subject, about the decision, maybe point out | debatable points, and assume that anyone who stays quiet agrees with you. | | Thanks, | 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

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee