<html><head></head><body><div><div></div><div><div class=""><div class=""><div class=""><div class="">I would just point out that decision by committee, and in particular the GHC Proposals process, has a high cost in terms of both total human brain cycles and latency. The cost is entirely justified when it comes to things that are a) hard to revert and b) extremely hard to get right the first time, like new extensions to the language, or c) very sensitive (like governance, say). For things like breaking changes to API's, it's worth writing out what the current problems are. Are users complaining that the API churn is too high? Are they concerned about endemic quality problems with the API?<br/></div><div class=""><br/></div><div class="">It may be enough to make sure to know who the main users of the API are and tag them as reviewers on these types of changes in GitLab. Or to avoid extra process but enshrine principles that might be necessary to adopt, like saying that existing API functions should always be kept as-is during some deprecation period and new functionality should be exposed in new additions to the API. Principles to be upheld by reviewers.</div></div></div><br/><div class=""><div class="gmail_quote">On Mon, Jul 27, 2020 at 10:45:50, Simon Peyton Jones <span dir="ltr" class=""><<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a>></span> wrote:<br/><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote" style="null" id="null">
<div class="WordSection1">
<p class="MsoNormal">A <a href="https://gitlab.haskell.org/ghc/ghc/-/merge_requests/3758" target="_blank" rel="noopener noreferrer">
recent MR for GHC</a> (adding machinery for plugins to write data to extensible interface files) made me wonder:
<br/></p>
<p style="margin-left:36.0pt" class="MsoNormal">how we should treat significant changes to the GHC API?<br/></p>
<p class="MsoNormal">Changes to the GHC API, especially to bits used by plugins or by IDEs, are clearly user-visible to an important class of users – they are not just internal to GHC itself. So, how should we review them? Should they perhaps be part of
the GHC proposals process? Or some other similar process? (The collection of experts on the GHC API, plugins, IDEs etc, is rather different to the membership of the GHC steering group.)<br/></p>
<p class="MsoNormal">I'm asking, not to be obstructive, but because the GHC API deserves to be thought of as a whole; in the past it has grown incrementally, without much discussion, and that has not served us well. But at the moment there is no process, no
group to consult.<br/></p>
<p class="MsoNormal">Any views?<br/></p>
<p class="MsoNormal">Simon<br/></p>
</div>
<p class="">_______________________________________________
<br/>
ghc-devs mailing list
<br/>
<a target="_blank" rel="noopener noreferrer" href="mailto:ghc-devs@haskell.org">ghc-devs@<wbr/>haskell.<wbr/>org</a>
<br/>
<a target="_blank" rel="noopener noreferrer" href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs">http:/<wbr/>/<wbr/>mail.<wbr/>haskell.<wbr/>org/<wbr/>cgi-bin/<wbr/>mailman/<wbr/>listinfo/<wbr/>ghc-devs</a></p></div></div></blockquote></div></div></div><div><br/></div></div></div></body></html>