<html><body><div dir="ltr">
    Dear Committee,</div><div dir="ltr"><br></div><div dir="ltr">As far as I understand, the proposal now allows annotations before classes/instances/types/… to appear either in its own line or before the thing, by making semicolons optional (which would be introduced during parsing if we use a newline).</div><div dir="ltr"><br></div><div dir="ltr">I think the proposal is ready for acceptance, if no more problems pop up.</div><div dir="ltr"><br></div><div dir="ltr">Regards,</div><div dir="ltr">Alejandro</div><div dir="ltr"><br><br>
    <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">El 17 dic 2021 23:18:35, Richard Eisenberg <<a href="mailto:lists@richarde.dev">lists@richarde.dev</a>> escribió:<br></div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" type="cite">
            <div><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></div><div style="word-wrap:break-word;line-break:after-white-space" class="">I've updated the proposal to include an optional semicolon: <a href="https://github.com/goldfirere/ghc-proposals/blob/clarify-modifiers/proposals/0370-modifiers.rst" class="">https://github.com/goldfirere/ghc-proposals/blob/clarify-modifiers/proposals/0370-modifiers.rst</a><div class=""><br class=""></div><div class="">Richard<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 26, 2021, at 1:45 PM, Richard Eisenberg <<a href="mailto:lists@richarde.dev" class="">lists@richarde.dev</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap:break-word;line-break:after-white-space" class="">I like the idea of allowing the semicolon, but I believe it should be optional, as I stated on GitHub: <a href="https://github.com/ghc-proposals/ghc-proposals/pull/390#issuecomment-878296938" class="">https://github.com/ghc-proposals/ghc-proposals/pull/390#issuecomment-878296938</a><div class=""><br class=""></div><div class="">I'm content to add the (optional) semicolon to #392.</div><div class=""><br class=""></div><div class="">I don't know about the practical ramifications. Vlad may be best positioned to answer that.</div><div class=""><br class=""></div><div class="">Richard<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Jul 23, 2021, at 3:53 AM, Alejandro Serrano Mena <<a href="mailto:trupill@gmail.com" class="">trupill@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div dir="ltr" class="">
    Dear all,</div><div dir="ltr" class="">Richard has now updated the proposal, but only Arnaud has commented on it. I think this requires a few more eyes, since it will permeate the language once people start using linear types, and we are already thinking about introducing modifiers in other parts.</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">In fact, I’ve realised that there’s a (grammar) conflict between this proposal and <a href="https://github.com/ghc-proposals/ghc-proposals/pull/390" class="">https://github.com/ghc-proposals/ghc-proposals/pull/390</a> (the fine-grained pragmas for type classes and instances). This proposal defines</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class=""><table class=" diff-table tab-size js-diff-table"><tbody class=""><tr class=""><td class="blob-code blob-code-addition"><span class="blob-code-inner blob-code-marker">topdecl ::= {modifier} 'type' simpletype '=' type</span></td></tr><tr class=""></tr></tbody></table><table class=" diff-table tab-size js-diff-table"><tbody class=""><tr class=""><td class="blob-code blob-code-addition"><span class="blob-code-inner blob-code-marker">| {modifier} 'data' [context '=>'] simpletype ['=' constrs] [deriving]</span></td></tr><tr class=""></tr></tbody></table><table class=" diff-table tab-size js-diff-table"><tbody class=""><tr class=""><td class="blob-code blob-code-addition"><span class="blob-code-inner blob-code-marker">| {modifier} 'newtype' [context '=>'] simpletype = newconstr [deriving]</span></td></tr><tr class=""></tr></tbody></table><table class=" diff-table tab-size js-diff-table"><tbody class=""><tr class=""><td class="blob-code blob-code-addition"><span class="blob-code-inner blob-code-marker">| {modifier} 'class' [scontext '=>'] tycls tyvar ['where' cdecls]</span></td></tr><tr class=""></tr></tbody></table><span class="blob-code-inner blob-code-marker">| {modifier} 'instance' [scontext '=>'] qtycls inst ['where' idecls]</span></div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">But #390 defines (note the ; at the end of the modifiers block):</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class=""><table class=" diff-table tab-size js-diff-table"><tbody class=""><tr class=""><td class="blob-code is-hovered blob-code-addition"><span class="blob-code-inner blob-code-marker">modifiers : {- empty -} | ('%' qtycon)* ';'</span></td></tr></tbody></table><table class=" diff-table tab-size js-diff-table"><tbody class=""><tr class=""><td class="blob-code blob-code-addition"><span class="blob-code-inner blob-code-marker">cl_decl</span> : modifiers 'class' tycl_hdr fds where_cls</td></tr></tbody></table><div dir="ltr" class=""><br class=""></div>I guess we should sort this out before accepting any of them.</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Alejandro<br class=""><br class="">
    <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">El 28 jun 2021 21:26:45, Alejandro Serrano Mena <<a href="mailto:trupill@gmail.com" class="">trupill@gmail.com</a>> escribió:<br class=""></div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div class=""><div class=""><div dir="" class=""><div dir="ltr" class="">Richard, will you take care of making those small changes to the proposal? That way we could mark this as accepted.</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Regards,</div><div dir="ltr" class="">Alejandro<br class=""><br class="">
    <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">El 28 jun 2021 9:01:28, Spiwack, Arnaud <<a href="mailto:arnaud.spiwack@tweag.io" class="">arnaud.spiwack@tweag.io</a>> escribió:<br class=""></div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div dir="ltr" class="">Yes, I believe that Richard and I are in agreement now. I don't think all the conclusions have been added to the proposal yet, though; but whatever's left, it's fairly minor.<br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 24, 2021 at 1:29 PM Alejandro Serrano Mena <<a href="mailto:trupill@gmail.com" class="">trupill@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div dir="" class=""><div dir="ltr" class="">
    Dear all,</div><div dir="ltr" class="">This discussion has been dormant for some time, but it’s time to revive it!</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Richard, Arnaud, did you manage to reach conclusion about the modification to the proposal?</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Apart from that, is there any other concern about the proposal? As I said in my original message, this is a very small amendment to an already-existing proposal, so if we accepted the previous one I see no problem in this one. I’ll wait until Richard and Arnaud get back on the issue, and then assume that silence for a week is acceptance.</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Regards,</div><div dir="ltr" class="">Alejandro</div><div dir="ltr" class=""><br class="">
    <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">El 11 jun 2021 14:55:41, Spiwack, Arnaud <<a href="mailto:arnaud.spiwack@tweag.io" target="_blank" class="">arnaud.spiwack@tweag.io</a>> escribió:<br class=""></div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div dir="ltr" class=""><div class="">I think that my discussion with Richard has come to a conclusion (it should incur a small modification to the proposal).</div><div class=""><br class=""></div><div class="">It is a very small (amendment to a) proposal, let's find a consensus on this one quickly.<br class=""></div><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 12, 2021 at 11:26 AM Spiwack, Arnaud <<a href="mailto:arnaud.spiwack@tweag.io" target="_blank" class="">arnaud.spiwack@tweag.io</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><div class="">I've commented on the PR [ <a href="https://github.com/ghc-proposals/ghc-proposals/pull/392#pullrequestreview-657652189" target="_blank" class="">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 class=""><br class=""></div><div class="">But mostly, I'm worried about the implications/interactions that these changes have with linear types.</div><div class=""><br class=""></div><div class="">(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 class=""></div></div><br class=""><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" target="_blank" class="">trupill@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div dir="" class=""><div dir="ltr" class="">
    Dear Committee,</div><div dir="ltr" class="">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" class=""><br class=""></div><div dir="ltr" class="">Regards,</div><div dir="ltr" class="">Alejandro<br class=""><br class="">
    <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" class="">mail@joachim-breitner.de</a>> wrote:<br class=""></div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            
<div class="">
<div class="">
    Dear Committe,<br class=""><br class="">Clarify modifiers design principle<br class="">has been proposed by Richard<br class=""><a href="https://github.com/ghc-proposals/ghc-proposals/pull/392" target="_blank" class="">https://github.com/ghc-proposals/ghc-proposals/pull/392</a><br class=""><br class="">This is an amendmend to #370, see the PR description for links to diffs<br class="">etc.<br class=""><br class="">I propose Alejandro as the shepherd, as he shepherded #370 before.<br class=""><br class="">Please guide us to a conclusion as outlined in <br class=""><a href="https://github.com/ghc-proposals/ghc-proposals#committee-process" target="_blank" class="">https://github.com/ghc-proposals/ghc-proposals#committee-process</a><br class=""><br class="">Thanks,<br class="">Joachim<br class="">-- <br class="">-- <br class="">Joachim Breitner<br class="">  <a href="mailto:mail@joachim-breitner.de" target="_blank" class="">mail@joachim-breitner.de</a><br class="">  <a href="http://www.joachim-breitner.de/" target="_blank" class="">http://www.joachim-breitner.de/</a><br class=""><br class=""><br class="">_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""><a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class=""><a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" target="_blank" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br class="">
</div>
</div>
        </blockquote>
    </div>
</div></div></div>
_______________________________________________<br class="">
ghc-steering-committee mailing list<br class="">
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank" class="">ghc-steering-committee@haskell.org</a><br class="">
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br class="">
</blockquote></div>
</blockquote></div>

        </blockquote>
    </div>
</div></div></div>
</blockquote></div>

        </blockquote>
    </div>
</div></div></div></div>

        </blockquote>
    </div>
</div></div>
_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""><a href="mailto:ghc-steering-committee@haskell.org" class="">ghc-steering-committee@haskell.org</a><br class=""><a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">ghc-steering-committee mailing list<br class=""><a href="mailto:ghc-steering-committee@haskell.org" class="">ghc-steering-committee@haskell.org</a><br class=""><a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br class=""></div></blockquote></div><br class=""></div></div></div>
        </blockquote>
    </div>
</div></body></html>