<div dir="ltr"><div>I've commented on the PR [ <a href="https://github.com/ghc-proposals/ghc-proposals/pull/392#pullrequestreview-657652189">https://github.com/ghc-proposals/ghc-proposals/pull/392#pullrequestreview-657652189</a> ] the changes on the syntax of lambda expressions are not motivated at all, I think at the very least there should be a discussion in the Alternatives section.</div><div><br></div><div>But mostly, I'm worried about the implications/interactions that these changes have with linear types.</div><div><br></div><div>(I'll be off for the rest of the week starting tonight, so I'll be back on this conversation on Monday, most likely)<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 11, 2021 at 10:10 AM Alejandro Serrano Mena <<a href="mailto:trupill@gmail.com">trupill@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir=""><div dir="ltr">
Dear Committee,</div><div dir="ltr">This proposal seems a natural extension of #370, covering some additional cases (modifiers to classes and other declarations) that we’ve found along the way. My recommendation is acceptance.</div><div dir="ltr"><br></div><div dir="ltr">Regards,</div><div dir="ltr">Alejandro<br><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On 4 May 2021 at 09:41:56, Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>
Dear Committe,<br><br>Clarify modifiers design principle<br>has been proposed by Richard<br><a href="https://github.com/ghc-proposals/ghc-proposals/pull/392" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/392</a><br><br>This is an amendmend to #370, see the PR description for links to diffs<br>etc.<br><br>I propose Alejandro as the shepherd, as he shepherded #370 before.<br><br>Please guide us to a conclusion as outlined in <br><a href="https://github.com/ghc-proposals/ghc-proposals#committee-process" target="_blank">https://github.com/ghc-proposals/ghc-proposals#committee-process</a><br><br>Thanks,<br>Joachim<br>-- <br>-- <br>Joachim Breitner<br> <a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br> <a href="http://www.joachim-breitner.de/" target="_blank">http://www.joachim-breitner.de/</a><br><br><br>_______________________________________________<br>ghc-steering-committee mailing list<br><a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br><a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</div>
</div>
</blockquote>
</div>
</div></div></div>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div>