<div dir="ltr"><div dir="ltr">On Fri, 1 Sept 2023 at 17:17, Simon Marlow <<a href="mailto:marlowsd@gmail.com">marlowsd@gmail.com</a>> wrote:</div><div class="gmail_quote"><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"><div>A few things make this not a straightforward thumbs up for me, though I'm not strongly against.<br></div><div><br></div><div>What is the interaction with GHC20xx? Presumably we want to say something like GHC20xx will never include any Deprecated or Legacy extensions? What about Unsable? if an extension transitions from Stable -> Legacy, would we remove it from the next GHC20xx?</div></div></blockquote><div><br></div><div>Ah, I just noticed that the proposal does say something about this:</div><div><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>For existing, or future, language sets such as <code>GHC2021</code> or <code>Haskell98</code>, it is expected that none of the contained extensions would be <code>Unstable</code>.
However, this proposal does not seek to impose any particular policy on
the inclusion of extensions into language sets - the developers and the
steering committee are always in the best position to make a decision
about a concrete extension and extension set.</div></blockquote><div> </div><div>OK.</div><div><br></div><div>Simon</div><div><br></div><div><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="ltr"><div><br></div><div>Something doesn't feel quite right about the warning system. If a module can start with</div><div><br></div><div><font face="monospace">{-# OPTIONS_GHC -Wno-XDeprecated #-}</font></div><div><font face="monospace">{-# LANGUAGE OverlappingInstances #-}</font></div><div><font face="monospace"><br></font></div><div><font face="arial,sans-serif">and silently use an extension that the {build system, user, project} wanted to disallow, have we achieved anything? Compare this to the current situation, where the environment can say -XNoOverlappingInstances and code can override that with {-# LANGUAGE OverlappingInstances #-} - there's essentially no difference, we just added another layer of disable/override that isn't buying us anything.<br></font></div><div><font face="arial,sans-serif"><br></font></div><div><font face="arial,sans-serif">(note I'm viewing this through the spectacles of -Werror, because I've come to believe that warnings are essentially not useful unless given teeth with -Werror.)</font></div><div><font face="arial,sans-serif"><br></font></div><div><font face="arial,sans-serif">Cheers</font></div><div><font face="arial,sans-serif">Simon<br></font></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 1 Sept 2023 at 13:18, Vladislav Zavialov <<a href="mailto:vlad.z.4096@gmail.com" target="_blank">vlad.z.4096@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="ltr"><div dir="ltr">I agree that we need a categorisation of extension language flags, but I'm not convinced that {Stable, Unstable, Deprecated, Legacy} is the right set of labels. In fact, I wouldn't want to commit to any particular categorisation before we actually go through all the extensions in GHC and see for ourselves that they can be adequately categorized according to the proposed system.<div><br></div><div>The proposal says "classifications of individual language extensions will be left to a future proposal". Well, I am skeptical that this separation makes sense. I would much prefer if we were discussing a concrete categorisation proposal, not just a set of four labels whose implications I can't fully grasp.</div><div></div><div><br></div><div>Vlad</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 1, 2023 at 11:37 AM Simon Peyton Jones <<a href="mailto:simon.peytonjones@gmail.com" target="_blank">simon.peytonjones@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="ltr"><div dir="ltr"><div style="font-family:tahoma,sans-serif">Dear Simon, Vlad, Eric, Chris, Moritz</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">I would love to hear from you about this proposal. <b>Please</b>. <br></div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">I plan to accept it unless I hear dissent. But I would much rather have an explicit response from you than take silence as assent. You are a member of the committee, after all!</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">My apologies if I have missed your reply<br></div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">Simon</div></div></div>
</blockquote></div>
</div>
</blockquote></div>
</blockquote></div></div>