[ghc-steering-committee] Do we consider the GHC API in scope?

Joachim Breitner mail at joachim-breitner.de
Mon Feb 5 22:42:00 UTC 2018


Hi,

in https://github.com/ghc-proposals/ghc-proposals/pull/108 David
proposed changes to the plugin API. The propsosal is still under
discussion (so if you want to comment, do it there), but more
generally, I wonder:

Is the GHC API (including the one for plugins) in scope for the GHC
steering committee?

Or should they go the same route as other, genuinely internal changes
in GHC, which would be Trac and Phab?

Note that plugins often have to import arbitrary GHC modules, not just
GhcPlugins, so really every exported function in GHC is part of the GHC
API and hence the plugin API?

Cheers,
Joachim

-- 
Joachim Breitner
  mail at joachim-breitner.de
  http://www.joachim-breitner.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20180205/9a1df77d/attachment.sig>


More information about the ghc-steering-committee mailing list