GHC API question: resolving dependencies for modules

[Ben Gamari]

Dmitriy Kovanikov <kovanikov at gmail.com> writes:

> Thanks a lot for your suggestion! I’ve looked into GHC source plugins. 
> And, specifically, into your `hashtag-coerce` example:
>
> * https://github.com/mpickering/hashtag-coerce <https://github.com/mpickering/hashtag-coerce>
>
> As far as I can see, this allows only to analyse source code (to
> produce warnings or errors).

It depends upon which type of source plugin you are using. There are a
few points in the compilation pipeline that source plugins allow you to
plug in to. Some of these allow the plugin to modify the AST while
others only allow inspection. See the users guide [1] for details.

Cheers,

- Ben


[1] https://github.com/ghc/ghc/blob/master/docs/users_guide/extending_ghc.rst#source-plugins
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20180625/7fb9f7fc/attachment.sig>