<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>My original motivation for !1580 and !1827 (the latter of which
ended up getting merged) would be equally well supported by an
interface with more limited scope. My only requirement there was
to be able to override the meta hook. I therefore would not mind
going back to the approach I initially took, in !1580, which I
preferred back then already. As long as we leave a way for plugins
to override hooks, my use case will not suffer.<br>
</p>
<div class="moz-cite-prefix">On 14/09/2020 21:20, Ben Gamari wrote:<br>
</div>
<blockquote type="cite" cite="mid:878sdckvxb.fsf@smart-cactus.org">
<pre class="moz-quote-pre" wrap="">Moritz Angermann <a class="moz-txt-link-rfc2396E" href="mailto:moritz.angermann@gmail.com"><moritz.angermann@gmail.com></a> writes:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I believe this to already be broken in HEAD. DynFlags already got quite an
overhaul/break. I'd rather we drop supporting DynFlagPlugins. And
offer alternative stable interfaces. Though to be honest, I believe our
Plugin story is rather poor so far.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">To fill in a bit of history here, DynFlags plugins were introduced in
!1827, which arose as an alternative to !1580. The latter proposed a
much more specialised interface specifically allowing plugins to
introduce Hooks. Personally, I far prefer the approach taken in !1580. To
quote my comment on !1580:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I agree that overriding DynFlags is excessive and, moreover, it
entrenches the structure of DynFlags as a semi-stable interface. In my
opinion the current state of DynFlags is a very uneasy compromise and
really should be refactored (at very least split up into smaller
records). While it's true that the Hsc capability given to parser
plugins allows DynFlags to be modified, I would consider this to be
very much a backdoor and not a supported use.
Hooks, on the other hand, are intended to be extension points for the
compiler. Consequently it is quite natural for them to be set by
plugins.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
In light of how quickly DynFlags is now changing, I somewhat regret not
pushing back more vigorously against the DynFlags-centric approach. I
tend to agree that we should remove the interface and revert to a more
limited interface that simply deals in Hooks.
Cheers,
- Ben
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ghc-devs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a>
<a class="moz-txt-link-freetext" href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a>
</pre>
</blockquote>
</body>
</html>