<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">I too am concerned that the author @strake has not responded since Oct 2022.   Nor have we seen a chorus of support from other users.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">My suggestion</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><ul><li>Park the proposal for now</li><li>Reach out to the author to check that they are OK</li></ul><div>Simon M: you are shepherding; what do you think?</div><div><br></div><div>Simon<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 2 Oct 2023 at 09:07, Adam Gundry <<a href="mailto:adam@well-typed.com">adam@well-typed.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">I'm unconvinced by the current state of this proposal, for similar <br>
reasons as Simon PJ gives on the proposal thread <br>
(<a href="https://github.com/ghc-proposals/ghc-proposals/pull/526#issuecomment-1740735610" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/526#issuecomment-1740735610</a>).<br>
<br>
If we want to accept this merely for reasons of consistency, I think the <br>
simplest way forward would be to not introduce a new extension name, and <br>
instead define the combination of MonadComprehensions + ApplicativeDo to <br>
do what the proposal suggests.<br>
<br>
The author doesn't seem to be responsive on the thread. While I worry <br>
this may be because of the time the proposal process has been taking, it <br>
makes it difficult to gauge support for the various alternative <br>
suggestions that have been made.<br>
<br>
Cheers,<br>
<br>
Adam<br>
<br>
<br>
On 28/09/2023 08:12, Simon Marlow wrote:<br>
> Dear committee,<br>
> <br>
> #526 proposes a new extension ApplicativeComprehensions (implying <br>
> MonadComprehensions). It would provide the equivalent of the current <br>
> ApplicativeDo desugaring for do-expressions to list comprehensions.<br>
> <br>
>   * Github thread <<a href="https://github.com/ghc-proposals/ghc-proposals/pull/526" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/526</a>><br>
>   * Rendered<br>
>     <<a href="https://github.com/strake/ghc-proposals/blob/acomp/proposals/0000-applicative-comprehensions.rst" rel="noreferrer" target="_blank">https://github.com/strake/ghc-proposals/blob/acomp/proposals/0000-applicative-comprehensions.rst</a>><br>
> <br>
> The extension itself is relatively uncontroversial, but there are some <br>
> unresolved quirks in the original ApplicativeDo extension which made us <br>
> uneasy about extending it. However, after various discussions I'm going <br>
> to propose accepting this proposal in its current state.  Rationale:<br>
> <br>
>   * It doesn't make things worse, and the implementation isn't likely to<br>
>     add significant complexity.<br>
>   * It retains consistency between ApplicativeDo and<br>
>     ApplicativeComprehensions (in contrast to the idea of making<br>
>     ApplicativeComprehensions perform a simpler desugaring, which came<br>
>     up during the discussion)<br>
>   * A future proposal can add a simpler version of the desugaring for<br>
>     both extensions later.<br>
> <br>
> <br>
> Cheers<br>
> Simon<br>
<br>
-- <br>
Adam Gundry, Haskell Consultant<br>
Well-Typed LLP, <a href="https://www.well-typed.com/" rel="noreferrer" target="_blank">https://www.well-typed.com/</a><br>
<br>
Registered in England & Wales, OC335890<br>
27 Old Gloucester Street, London WC1N 3AX, England<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>