Tooling-friendly ModSummary

Alan & Kim Zimmerman alan.zimm at gmail.com
Mon Sep 5 18:32:49 UTC 2016


And I gather I can do this with the compiler hooks.

Alan

On Mon, Sep 5, 2016 at 8:27 PM, Alan & Kim Zimmerman <alan.zimm at gmail.com>
wrote:

> At the moment the standard way to use the GHC API is something like
>
>                         _ <- load LoadAllTargets
>                         modSum <- getModSummary mn
>                         p <- parseModule modSum
>
> And likewise if renamed or typechecked ASTs are needed.
>
> But the `load` step already does all those phases.
>
> So, would there be any objection to modifying the ModSummary to possibly
> retain those artifacts, configurable via a DynFlag?
>
> I would expect the flag would default to retaining none, but could then
> either provide for returning all artifacts, or just for the targets
> explicitly listed in the `setTargets` call (i.e. not the full `depanal`
> result).
>
> Regards
>   Alan
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20160905/d9e73933/attachment-0001.html>


More information about the ghc-devs mailing list