
Hi, accepted, with using -XLambdaCase. Thanks all! Cheers, Joachim Am Samstag, dem 18.09.2021 um 12:40 +0300 schrieb Vitaly Bragilevsky:
I've voted to extend LambdaCase. I prefer thinking that the backward incompatibility problem, in this case, is negligible.
Vitaly
пт, 17 сент. 2021 г. в 13:25, Simon Peyton Jones via ghc-steering- committee
: Vitaly, Tom Are you there? I’d love to hear from you about this. Thanks Simon PS: I am leaving Microsoft at the end of November 2021, at which pointsimonpj@microsoft.com will cease to work. Usesimon.peytonjones@gmail.com instead. (For now, it just forwards to simonpj@microsoft.com.) From: Simon Peyton Jones
Sent: 15 September 2021 13:00 To: ghc-steering-committee@haskell.org Cc: Simon Peyton Jones Subject: RE: [ghc-steering-committee] Proposal #302: Multiway lambda: new extension or not? Vitaly, Eric, Tom, Alejandro As Joachim says, we need to make a decision on the LambdaCase flag issue. It’s a judgement call, so let’s just vote. Here is the voting sheet. I have filled in votes from Simon, myself, Joacim, Richard, Vlad. But four of us (in the to: line) have not expressed an opinion. Could you do so please, in the next day or two? It should take you 5 minutes. Thanks Simon PS: I am leaving Microsoft at the end of November 2021, at which pointsimonpj@microsoft.com will cease to work. Usesimon.peytonjones@gmail.com instead. (For now, it just forwards tosimonpj@microsoft.com.) | -----Original Message----- | From: ghc-steering-committee On Behalf Of Joachim Breitner | Sent: 14 September 2021 08:39 | To: ghc-steering-committee@haskell.org | Subject: Re: [ghc-steering-committee] Proposal #302: Multiway lambda: | new extension or not? | | Hi, | | | on the multiway-lambda story, we have voted to add \cases alongside | \case. But one open question is still: Do we | (1) add -XLambdaCases (which would imply -XLambdaCase) or | (2) simply expand the meaning of -XLambdaCase. | | On the Github thread at | https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith | ub.com%2Fghc-proposals%2Fghc- proposals%2Fpull%2F302%23issuecomment- | 895080031&data=04%7C01%7Csimonpj%40microsoft.com%7Cea35a8831943 459 | 9cce708d97752bd08%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6376 720 | 20597687362%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l uMz | IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=2ySitCA%2FT1uUzne zDY | UKIO8g2ImLMKlnxm1OpKOXKZg%3D&reserved=0 | we see that I lean towards (1), but SPJ leands towards (2). | | It doesn’t matter that much, but we need to make a decision. Can I | please get some opinions from the rest of the committee on this point? | | Cheers, | Joachim | | | -- | Joachim Breitner | mail@joachim-breitner.de | | https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.j | oachim- | breitner.de%2F&data=04%7C01%7Csimonpj%40microsoft.com%7Cea35a88 319 | 434599cce708d97752bd08%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7 C63 | 7672020597697367%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj oiV | 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=unmdYu9zUy00 ec4 | 21KJYmL9I2ZO%2BlIx5J9cLw27GnmI%3D&reserved=0 | | | _______________________________________________ | ghc-steering-committee mailing list | ghc-steering-committee@haskell.org | https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail | .haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering- | committee&data=04%7C01%7Csimonpj%40microsoft.com%7Cea35a8831943 459 | 9cce708d97752bd08%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6376 720 | 20597697367%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l uMz | IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=TG3t%2Fw1kFLk173S oM5 | soHU39BlAPv76TY%2B9FNetaLJs%3D&reserved=0 _______________________________________________ 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/