Please review #368: Warn on prefix/suffix operators, Shepherd: Tom
Dear Committee, this is your secretary speaking: Warn on prefix/suffix operators has been proposed by Richard https://github.com/ghc-proposals/ghc-proposals/pull/368 This is an amendment to #229 (Whitespace-sensitive operator parsing), see the PR description linked above for details. I’ll propose Tom as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Thanks, Joachim -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
Hi all, Richard has proposed a small change to the previously accepted “Whitespace-sensitive operator parsing” proposal (whose current state is rendered here<https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0229-whitespace-bang-patterns.rst>), specifically to say that the described warning be triggered by -Wall and -Wcompat. I think this is sensible and hopefully not particularly controversial, and I recommend that we accept. The updated proposal may be viewed here<https://github.com/goldfirere/ghc-proposals/blob/88690a542ada41dccd0f58d252ed6d392140034d/proposals/0000-prefix-suffix-operators.rst#proposed-change-specification>; please reply with any thoughts/concerns! Thanks, Tom On 9 Jan 2021, at 16:43, Joachim Breitner <mail@joachim-breitner.de<mailto:mail@joachim-breitner.de>> wrote: Dear Committee, this is your secretary speaking: Warn on prefix/suffix operators has been proposed by Richard https://github.com/ghc-proposals/ghc-proposals/pull/368 This is an amendment to #229 (Whitespace-sensitive operator parsing), see the PR description linked above for details. I’ll propose Tom as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process 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
I have no opinion either way. (which, I think, for such a small change counts as a thumb up) On Fri, Jan 15, 2021 at 4:10 PM Tom Harding <tomjharding@live.co.uk> wrote:
Hi all,
Richard has proposed a small change to the previously accepted “Whitespace-sensitive operator parsing” proposal (whose current state is rendered here <https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0229-whitespace-bang-patterns.rst>), specifically to say that the described warning be triggered by -Wall and -Wcompat. I think this is sensible and hopefully not particularly controversial, and I recommend that we accept.
The updated proposal may be viewed here <https://github.com/goldfirere/ghc-proposals/blob/88690a542ada41dccd0f58d252ed6d392140034d/proposals/0000-prefix-suffix-operators.rst#proposed-change-specification>; please reply with any thoughts/concerns!
Thanks, Tom
On 9 Jan 2021, at 16:43, Joachim Breitner <mail@joachim-breitner.de> wrote:
Dear Committee,
this is your secretary speaking:
Warn on prefix/suffix operators has been proposed by Richard https://github.com/ghc-proposals/ghc-proposals/pull/368
This is an amendment to #229 (Whitespace-sensitive operator parsing), see the PR description linked above for details.
I’ll propose Tom as the shepherd.
Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process
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
I'm mildly in support, of this. Certainly no objection. Simon From: ghc-steering-committee <ghc-steering-committee-bounces@haskell.org> On Behalf Of Tom Harding Sent: 15 January 2021 15:10 To: ghc-steering-committee@haskell.org Subject: Re: [ghc-steering-committee] Committee review #368: Warn on prefix/suffix operators Hi all, Richard has proposed a small change to the previously accepted "Whitespace-sensitive operator parsing" proposal (whose current state is rendered here<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fblob%2Fmaster%2Fproposals%2F0229-whitespace-bang-patterns.rst&data=04%7C01%7Csimonpj%40microsoft.com%7C76560bb645744aa5375008d8b967b535%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637463203409053387%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=TKmreV4ZQNfkuEQxQcW0RthF%2FZfY49TIOEIvwxNg70s%3D&reserved=0>), specifically to say that the described warning be triggered by -Wall and -Wcompat. I think this is sensible and hopefully not particularly controversial, and I recommend that we accept. The updated proposal may be viewed here<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoldfirere%2Fghc-proposals%2Fblob%2F88690a542ada41dccd0f58d252ed6d392140034d%2Fproposals%2F0000-prefix-suffix-operators.rst%23proposed-change-specification&data=04%7C01%7Csimonpj%40microsoft.com%7C76560bb645744aa5375008d8b967b535%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637463203409063388%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=TIqqic9hrWYeYvO%2BPdfpIeq947WTXmlwRjmY7QxpEJ8%3D&reserved=0>; please reply with any thoughts/concerns! Thanks, Tom On 9 Jan 2021, at 16:43, Joachim Breitner <mail@joachim-breitner.de<mailto:mail@joachim-breitner.de>> wrote: Dear Committee, this is your secretary speaking: Warn on prefix/suffix operators has been proposed by Richard https://github.com/ghc-proposals/ghc-proposals/pull/368<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fghc-proposals%2Fghc-proposals%2Fpull%2F368&data=04%7C01%7Csimonpj%40microsoft.com%7C76560bb645744aa5375008d8b967b535%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637463203409063388%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=FbBvVvq8XeopvQxbsEG7Jm4xcWAh9LesgBAcAX0%2FMhw%3D&reserved=0> This is an amendment to #229 (Whitespace-sensitive operator parsing), see the PR description linked above for details. I'll propose Tom as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Thanks, Joachim -- Joachim Breitner mail@joachim-breitner.de<mailto:mail@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
Looks sensible to me. Alejandro On 15 Jan 2021 at 16:09:59, Tom Harding <tomjharding@live.co.uk> wrote:
Hi all,
Richard has proposed a small change to the previously accepted “Whitespace-sensitive operator parsing” proposal (whose current state is rendered here <https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0229-whitespace-bang-patterns.rst>), specifically to say that the described warning be triggered by -Wall and -Wcompat. I think this is sensible and hopefully not particularly controversial, and I recommend that we accept.
The updated proposal may be viewed here <https://github.com/goldfirere/ghc-proposals/blob/88690a542ada41dccd0f58d252ed6d392140034d/proposals/0000-prefix-suffix-operators.rst#proposed-change-specification>; please reply with any thoughts/concerns!
Thanks, Tom
On 9 Jan 2021, at 16:43, Joachim Breitner <mail@joachim-breitner.de> wrote:
Dear Committee,
this is your secretary speaking:
Warn on prefix/suffix operators has been proposed by Richard https://github.com/ghc-proposals/ghc-proposals/pull/368
This is an amendment to #229 (Whitespace-sensitive operator parsing), see the PR description linked above for details.
I’ll propose Tom as the shepherd.
Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process
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
Hi Joachim, After two weeks and no thumbs down, I think we should mark this one as accepted! Thanks, Tom On 18 Jan 2021, at 21:03, Alejandro Serrano Mena <trupill@gmail.com<mailto:trupill@gmail.com>> wrote: Looks sensible to me. Alejandro On 15 Jan 2021 at 16:09:59, Tom Harding <tomjharding@live.co.uk<mailto:tomjharding@live.co.uk>> wrote: Hi all, Richard has proposed a small change to the previously accepted “Whitespace-sensitive operator parsing” proposal (whose current state is rendered here<https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0229-whitespace-bang-patterns.rst>), specifically to say that the described warning be triggered by -Wall and -Wcompat. I think this is sensible and hopefully not particularly controversial, and I recommend that we accept. The updated proposal may be viewed here<https://github.com/goldfirere/ghc-proposals/blob/88690a542ada41dccd0f58d252ed6d392140034d/proposals/0000-prefix-suffix-operators.rst#proposed-change-specification>; please reply with any thoughts/concerns! Thanks, Tom On 9 Jan 2021, at 16:43, Joachim Breitner <mail@joachim-breitner.de<mailto:mail@joachim-breitner.de>> wrote: Dear Committee, this is your secretary speaking: Warn on prefix/suffix operators has been proposed by Richard https://github.com/ghc-proposals/ghc-proposals/pull/368 This is an amendment to #229 (Whitespace-sensitive operator parsing), see the PR description linked above for details. I’ll propose Tom as the shepherd. Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process Thanks, Joachim -- Joachim Breitner mail@joachim-breitner.de<mailto:mail@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 _______________________________________________ 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
Thanks, merged. Am Dienstag, den 02.02.2021, 10:24 +0000 schrieb Tom Harding:
Hi Joachim,
After two weeks and no thumbs down, I think we should mark this one as accepted!
Thanks, Tom
On 18 Jan 2021, at 21:03, Alejandro Serrano Mena <trupill@gmail.com> wrote:
Looks sensible to me.
Alejandro
On 15 Jan 2021 at 16:09:59, Tom Harding <tomjharding@live.co.uk> wrote:
Hi all,
Richard has proposed a small change to the previously accepted “Whitespace-sensitive operator parsing” proposal (whose current state is rendered here), specifically to say that the described warning be triggered by -Wall and -Wcompat. I think this is sensible and hopefully not particularly controversial, and I recommend that we accept.
The updated proposal may be viewed here; please reply with any thoughts/concerns!
Thanks, Tom
On 9 Jan 2021, at 16:43, Joachim Breitner <mail@joachim-breitner.de> wrote:
Dear Committee,
this is your secretary speaking:
Warn on prefix/suffix operators has been proposed by Richard https://github.com/ghc-proposals/ghc-proposals/pull/368
This is an amendment to #229 (Whitespace-sensitive operator parsing), see the PR description linked above for details.
I’ll propose Tom as the shepherd.
Please guide us to a conclusion as outlined in https://github.com/ghc-proposals/ghc-proposals#committee-process
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 -- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/
participants (5)
-
Alejandro Serrano Mena -
Joachim Breitner -
Simon Peyton Jones -
Spiwack, Arnaud -
Tom Harding