<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">I'm supportive. I do not have a well-informed view, but the amendment is born from practical experience, so I am pretty sure it's an improvement.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I'd love a bit more detail in the proposal (I have commented in one place) but I might be off-target and would yield to others' advice, including that of the author.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Simon<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 29 Oct 2024 at 19:37, 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">It seems Zubin updated the proposal to take account of Sebastian's <br>
concerns, but then discussion has tailed off. Are we now in a position <br>
to accept this proposal, or are there any remaining concerns?<br>
<br>
Cheers,<br>
<br>
Adam<br>
<br>
<br>
<br>
On 24/09/2024 07:44, Sebastian Graf wrote:<br>
> I think changes to the communication protocol *are* user-facing, in that <br>
> any change to the protocol could implies a breaking change between all <br>
> cabal releases in the future and all GHC releases in the past.<br>
> It appears that is the case for the planned release of <br>
> `semaphore-compat-2`, but I'm not 100% sure.<br>
> <br>
> In that light, I think it's good to discuss in a proposal to ensure we <br>
> do not sign off lightly on such breaking changes, in particular for <br>
> future versions of `semaphore-compat`.<br>
> <br>
> I will express support once compatibility and breaking changes are <br>
> properly addressed.<br>
> <br>
> Sebastian<br>
> <br>
> ------ Originalnachricht ------<br>
> Von "Arnaud Spiwack" <<a href="mailto:arnaud.spiwack@tweag.io" target="_blank">arnaud.spiwack@tweag.io</a> <br>
> <mailto:<a href="mailto:arnaud.spiwack@tweag.io" target="_blank">arnaud.spiwack@tweag.io</a>>><br>
> An "Simon Peyton Jones" <<a href="mailto:simon.peytonjones@gmail.com" target="_blank">simon.peytonjones@gmail.com</a> <br>
> <mailto:<a href="mailto:simon.peytonjones@gmail.com" target="_blank">simon.peytonjones@gmail.com</a>>><br>
> Cc <a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a> <br>
> <mailto:<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a>><br>
> Datum 24.09.2024 04:17:17<br>
> Betreff Re: [ghc-steering-committee] Please review #673: Amendment to <br>
> -jsem proposal #540<br>
> <br>
>> Quite frankly, this is barely any user-facing change at all. <br>
>> Technically the semaphore could previously be shared by non-Haskell <br>
>> processes in ways the updated proposal doesn't allow. But it's not <br>
>> really something people do. So it all sounds reasonable.<br>
>><br>
>> On Mon, 23 Sept 2024 at 19:10, Simon Peyton Jones <br>
>> <<a href="mailto:simon.peytonjones@gmail.com" target="_blank">simon.peytonjones@gmail.com</a> <mailto:<a href="mailto:simon.peytonjones@gmail.com" target="_blank">simon.peytonjones@gmail.com</a>>> wrote:<br>
>><br>
>> I'm happy to support too, but I would like to see presentational<br>
>> changes, so the final proposal makes sense when read in 5 yrs time.<br>
>><br>
>> Simon<br>
>><br>
>> On Sat, 21 Sept 2024 at 20:45, Malte Ott <<a href="mailto:malte.ott@maralorn.de" target="_blank">malte.ott@maralorn.de</a><br>
>> <mailto:<a href="mailto:malte.ott@maralorn.de" target="_blank">malte.ott@maralorn.de</a>>> wrote:<br>
>><br>
>> I agree.<br>
>><br>
>> On 2024-09-21 09:16, Eric Seidel wrote:<br>
>> > Hi all,<br>
>> ><br>
>> > This seems like a sensible update to an accepted proposal.<br>
>> ><br>
>> > I recommend we accept the amendment.<br>
>> ><br>
>> > Eric<br>
>> ><br>
>> > On Thu, Sep 19, 2024, at 19:00, Erik de Castro Lopo wrote:<br>
>> > > Hi all,<br>
>> > ><br>
>> > > This is minor updates to correct an existing approved<br>
>> proposal.<br>
>> > ><br>
>> > > I approve of these changes.<br>
>> > ><br>
>> > > Erik<br>
>> > ><br>
>> > > Adam Gundry wrote:<br>
>> > ><br>
>> > >> Dear Committee,<br>
>> > >><br>
>> > >> Zubin Duggal proposes to amend proposal #540, which<br>
>> introduced the -jsem<br>
>> > >> parallelism control mechanism, so that it can avoid<br>
>> incompatibilities<br>
>> > >> arising from different system C library implementations:<br>
>> > >><br>
>> > >> <a href="https://github.com/ghc-proposals/ghc-proposals/pull/673" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/673</a><br>
>> <<a href="https://github.com/ghc-proposals/ghc-proposals/pull/673" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/673</a>><br>
>> > >><br>
>> > >><br>
>> <a href="https://github.com/wz1000/ghc-proposals/blob/new-jsem/proposals/0540-jsem.rst" rel="noreferrer" target="_blank">https://github.com/wz1000/ghc-proposals/blob/new-jsem/proposals/0540-jsem.rst</a> <<a href="https://github.com/wz1000/ghc-proposals/blob/new-jsem/proposals/0540-jsem.rst" rel="noreferrer" target="_blank">https://github.com/wz1000/ghc-proposals/blob/new-jsem/proposals/0540-jsem.rst</a>><br>
>> > >><br>
>> > >> I'd like to nominate Eric Seidel as the shepherd, since<br>
>> he was the<br>
>> > >> shepherd of the original proposal.<br>
>> > >><br>
>> > >> Please guide us to a conclusion as outlined in<br>
>> > >><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> <<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>
>> > >> Cheers,<br>
>> > >><br>
>> > >> Adam<br>
<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>