<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I am sorry Simon,<div><br></div><div>Because I was so heavily involved in its preparation I assumed my support for the proposal was a given.</div><div><br></div><div>I enthusiastically support this proposal. I cannot overemphasise how import I think it is that</div><div><br></div><div> 1) we as a committee clarify for ourselves the status of these extensions and</div><div><br></div><div> 2) how useful I think it is for developers to have ready access such a definitive taxonomy.</div><div><br></div><div>Of course it doesn't solve all of our problems, but let's build on it and the feedback we get from the community.</div><div><br></div><div>Chris</div><div><div><br><blockquote type="cite"><div>On 1 Sep 2023, at 10:37, Simon Peyton Jones <simon.peytonjones@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Dear Simon, Vlad, Eric, Chris, Moritz</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I would love to hear from you about this proposal. <b>Please</b>. <br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" 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 class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">My apologies if I have missed your reply<br></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 Thu, 24 Aug 2023 at 16:42, Simon Peyton Jones <<a href="mailto:simon.peytonjones@gmail.com">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 style="font-family:tahoma,sans-serif">Dear GHC steering committee</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">A month ago I wrote to you concerning <a href="https://github.com/david-christiansen/ghc-proposals/blob/extension-lifecycle-proposal/proposals/0000-extension-lifecycle-framework.md" target="_blank">GHC Proposal 601 about GHC extensions</a>.</div><div style="font-family:tahoma,sans-serif"><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 style="font-family:tahoma,sans-serif">
We propose a categorization scheme for Haskell language extensions. This
scheme is simple, in that there are few categories that are described
in terms of the user-relevant aspects, and it is actionable, in that it
suggests concrete changes to the warning system of GHC that allow users
to express their own risk tolerance and get guidance as they upgrade
their compiler
</div></blockquote><div><br></div><div style="font-family:tahoma,sans-serif">It's holiday time I know, but still, I did not get a single reply. Is that because you all love it or you all hate it? RSVP!</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">I propose acceptance, modulo a few clarifications which I have posted on the discussion thread.</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">Please reply, yea or nay.</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">Simon<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 25 Jul 2023 at 15:58, 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 style="font-family:tahoma,sans-serif">Dear GHC Steering Committee</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif"><a href="https://github.com/david-christiansen/ghc-proposals/blob/extension-lifecycle-proposal/proposals/0000-extension-lifecycle-framework.md" target="_blank">Proposal #601</a> says <br></div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif;margin-left:40px">
We propose a categorization scheme for Haskell language extensions. This
scheme is simple, in that there are few categories that are described
in terms of the user-relevant aspects, and it is actionable, in that it
suggests concrete changes to the warning system of GHC that allow users
to express their own risk tolerance and get guidance as they upgrade
their compiler <br></div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">I'm happy with this proposal: it seems simple, comprehensible, and actionable. <br></div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">The only question in my mind is whether it is worth the bother. I'd love to hear from the practitioners on the committee.</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">But I propose that we accept it.</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">Simon<br></div><div style="font-family:tahoma,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 24 Jul 2023 at 14:39, 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">Dear Committee,<br>
<br>
David Thrane Christiansen suggested to categorize extensions into<br>
Experimental, Mature, Deprecated and Legacy, and add warning flag to<br>
GHC that allow users to be warned about (or shouted at for) using such<br>
extensions, if they choose so.<br>
<br>
<a href="https://github.com/ghc-proposals/ghc-proposals/pull/601" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/601</a><br>
<a href="https://github.com/david-christiansen/ghc-proposals/blob/extension-lifecycle-proposal/proposals/0000-extension-lifecycle-framework.md" rel="noreferrer" target="_blank">https://github.com/david-christiansen/ghc-proposals/blob/extension-lifecycle-proposal/proposals/0000-extension-lifecycle-framework.md</a><br>
<br>
Because of the meta-like aspect of this proposal, I’d like to assign<br>
this to Simon PJ.<br>
<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>
<br>
Cheers,<br>
Joachim<br>
<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>
</blockquote></div>
</blockquote></div></div>
</div></blockquote></div><br></div></body></html>