How should we treat changes to the GHC API?

Richard Eisenberg rae at richarde.dev
Tue Jul 28 02:57:58 UTC 2020



> On Jul 27, 2020, at 5:24 PM, John Ericson <john.ericson at obsidian.systems> wrote:
> 
> As permanent solution I don't like it, but as a stop gap to relieve any pressure for stability until we have sane interfaces, I *love* it.

I guess I'm arguing that ghc-lib (or something like it) should be the permanent solution. GHC will always be in flux internally.

Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20200728/87976d7d/attachment.html>


More information about the ghc-devs mailing list