<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_default" style="font-family:tahoma,sans-serif">
We have a feature in a stable compiler release, which we consider experimental, and thus reserve the right to break?
</div></blockquote><div style="font-family:tahoma,sans-serif" class="gmail_default"></div><div style="font-family:tahoma,sans-serif" class="gmail_default">I agree with this concern. </div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">Until recently we didn't have ghc-experimental, so there was no boundary between "experimental" and "stable". In another GHC proposal we are considering identifying "stable" extensions. Once both of those things in place we will have a clear line between things that we should really hesitate before changing, and things that are advertised as experimental and subject to change.</div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">Overloaded record fields are in the latter group, but we have had no way to advertise that fact. I'd love us to be able to.</div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">As there is supposedly a backwards compatible implementation for this, I’d like to ask for this to be considered in two steps:</div><div dir="auto">- backwards compatible change first.</div><div dir="auto">- deprecation and change of syntax second.</div></blockquote><div><br></div><div>If that's possible, it sounds plausible. Perhaps you can make the suggestion on the main discussion thread, and Adam can respond? <br></div></div><div style="font-family:tahoma,sans-serif" class="gmail_default"><br></div><div style="font-family:tahoma,sans-serif" class="gmail_default">Simon<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 22 Sept 2023 at 02:07, Moritz Angermann <<a href="mailto:moritz.angermann@gmail.com">moritz.angermann@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 dir="auto">I’m tempted to recuse myself as well on the technical merits of this proposal. As others might already expect, I am concerned about this breaking existing code. Do we have a rough estimate how much this will break?</div><div dir="auto"><br></div><div dir="auto">It also surfaces a topic we discussed just a short while ago. We have a feature in a stable compiler release, which we consider experimental, and thus reserve the right to break? I find this concept still fundamentally flawed. Anything that is part of stable compiler releases has to be considered stable by extension and thus needs to be treated with utmost care.</div><div dir="auto"><br></div><div dir="auto">I can see and fully support the wish to have a language reactor where things can be experimented with. But if we have this in our stable releases, it needs to be guarded in a way that users of those features have to actively opt in to it. I have people seen adopting this feature already, and I do not believe all of them are aware that this is a bleeding edge feature that can break without notice at any point in time.</div><div dir="auto"><br></div><div dir="auto">As there is supposedly a backwards compatible implementation for this, I’d like to ask for this to be considered in two steps:</div><div dir="auto">- backwards compatible change first.</div><div dir="auto">- deprecation and change of syntax second.</div><div dir="auto"><br></div><div dir="auto">Yes, this will be more work on behalf of the implementors. The burden of change is on the implementors, we can’t expect our users to cover the costs.</div><div dir="auto"><br></div><div dir="auto">For the second part, we should also have a thorough justification for the need to break. </div><div dir="auto"><br></div><div dir="auto">I’ll leave this with two links:</div><div dir="auto">Simon Marlow’s recent comment: <div><a href="https://mail.haskell.org/pipermail/ghc-steering-committee/2023-September/003432.html" target="_blank">https://mail.haskell.org/pipermail/ghc-steering-committee/2023-September/003432.html</a></div><div dir="auto">Dimitriis Tweet contrasting OCaml to Haskell: <div><a href="https://x.com/chshersh/status/1704886633856696831?s=46" target="_blank">https://x.com/chshersh/status/1704886633856696831?s=46</a></div></div></div><div dir="auto"><br></div><div dir="auto">Best</div><div dir="auto"> Moritz</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 22 Sep 2023 at 1:21 AM, 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">Hi,<br>
<br>
Am Donnerstag, dem 21.09.2023 um 09:37 +0200 schrieb Arnaud Spiwack:<br>
> Dear all.<br>
> <br>
> I submitted my recommendation 3 weeks ago, and only Simon has<br>
> commented yet. Please let me know your thoughts.<br>
<br>
I am essentially ignorant about anything related to records in Haskell,<br>
and will recuse myself, trusting y’all about this.<br>
<br>
Cheers,<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/" rel="noreferrer" target="_blank">http://www.joachim-breitner.de/</a><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></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>