<div dir="ltr"><div>Hi everybody,</div><div>The discussion in the GitHub thread seems to have come to a conclusion, and I encourage you to look at the proposal and give your opinion. The author of the proposal has written a very good introduction to the general idea of arrows that is quite useful (or at least has been for me!) to understand the context -> <a href="https://github.com/ghc-proposals/ghc-proposals/pull/303#issuecomment-631108435">https://github.com/ghc-proposals/ghc-proposals/pull/303#issuecomment-631108435</a></div><div><br></div><div>Everybody that has discussed there seems to be willing to break backwards-compatibility, as the scenario where it breaks is quite rare in practice. In fact, the goal of the proposal is to make those scenarios simpler, so that "control operators" can be more easily used and defined.</div><div><br></div><div>Note that the proposal also mentions some alternatives or points in the design space:</div><div>- Should the proposal be under a different extension or under `Arrows`?</div><div>- Should a flattened or nested tuple representation be used? This comments [<a href="https://github.com/ghc-proposals/ghc-proposals/pull/303#issuecomment-633199848">https://github.com/ghc-proposals/ghc-proposals/pull/303#issuecomment-633199848</a>] may give you some additional information.</div><div>- Should the type families described there be wired-in?</div><div><br></div><div>Looking forward to hearing from everyone. This is a complex proposal, with possible future ramifications. If there's no discussion in one week, I'll write again to the list.</div><div>Regards,</div><div>Alejandro<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El mar., 19 may. 2020 a las 9:02, Joachim Breitner (<<a href="mailto:mail@joachim-breitner.de">mail@joachim-breitner.de</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">
<div> <span>If there is active discussion, we usually put it back to the previous state, and wait for discussion to come to conclusions.<br><br></span>
<div>
<p>19.05.2020 08:36:42 Alejandro Serrano Mena <<a href="mailto:trupill@gmail.com" target="_blank">trupill@gmail.com</a>>:</p>
<blockquote>
<div dir="ltr">
<div>
Dear Committee,
</div>
<div>
When I took care of this proposal, the GitHub thread was quite dormant. However, it seems that right now there's quite some activity, and even proposals to completely redesign arrows. What is the right approach: let the discussion cool off, and then ask all of you to review the text (which I don't think is going to change substantially in any case) or move the proposal back to the previous state?
</div>
<div>
<br>
</div>
<div>
Alejandro
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
El vie., 15 may. 2020 a las 11:03, Richard Eisenberg (<<a href="mailto:rae@richarde.dev" target="_blank">rae@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">
<div>
I have some concerns -- mostly: is the improvement worth the implementation complexity? I've posted on GitHub.
<div>
<br>
</div>
<div>
Richard
<br>
<div>
<br>
<blockquote type="cite">
<div>
On May 15, 2020, at 8:01 AM, Alejandro Serrano Mena <<a href="mailto:trupill@gmail.com" target="_blank">trupill@gmail.com</a>> wrote:
</div>
<br>
<div>
<div dir="ltr">
<div>
Dear Committee,
</div>
<div>
This proposal looks good to me. The author has done a lot of work to formalize the new rules, and has done a check that no packages using arrow syntax would be broken by this modification. Thus, I recommend we accept this proposal.
</div>
<div>
<br>
</div>
<div>
Apart from the general discussion, I think it might be worth focusing on a specific part of the design: the use of a couple of type families to express "arrow stacks". I am not aware of other GHC extensions depending on particular type families.
</div>
<div>
- As the author discusses, these type families ought to be wired-in, so they can benefit from improvement during type checking. Is this a good choice? It looks to be, but other may have a different opinion.
</div>
<div>
- Would this type family pose a problem for optimization / specialization / ...?
</div>
<div>
<br>
</div>
<div>
Kind regards,
</div>
<div>
Alejandro
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
El lun., 4 may. 2020 a las 23:08, Joachim Breitner (<<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</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">
Dear Committee
<br>
<br> I took the liberty to re-asssign #303 to Alejandro; the authors
<br> rightfully asked for progress in the discussion thread.
<br>
<br> Cheers,
<br> Joachim
<br>
<br> Am Freitag, den 03.01.2020, 15:20 +0100 schrieb Joachim Breitner:
<br> > Dear Committee,
<br> >
<br> > this is your secretary speaking:
<br> >
<br> > Constraint based arrow notation
<br> > has been proposed by Aleix King
<br> > <a href="https://github.com/ghc-proposals/ghc-proposals/pull/303" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/303</a>
<br> > <a href="https://github.com/lexi-lambda/ghc-proposals/blob/constraint-based-arrow-notation/proposals/0000-constraint-based-arrow-notation.md" rel="noreferrer" target="_blank">https://github.com/lexi-lambda/ghc-proposals/blob/constraint-based-arrow-notation/proposals/0000-constraint-based-arrow-notation.md</a>
<br> >
<br> > I propose Chris Done as the shepherd.
<br> >
<br> > Please guide us to a conclusion as outlined in
<br> > <a href="https://github.com/ghc-proposals/ghc-proposals#committee-process" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals#committee-process</a>
<br> >
<br> > Thanks,
<br> > Joachim
<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/" rel="noreferrer" 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" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a>
<br>
</blockquote>
</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" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote></div>