Highlight differences of Frontend Plugin vs GHC API
There's many useful functionality in non-exposed modules. For example, ghc/Main.hs
contains doMake
[0], which is a one-shop stop for compiling all (non-Haskell + Haskell) source files. Now a GHC API client has to replicate much of this logic to get GHC-alike behavior.
Similarly for parseModeFlags
. Or is the intent here to encourage using of Frontend plugins instead of relying on these internals?
[0]: http://stuff.codereview.me/#ghc/ghc/Main.hs?corpus=ghc-8.2.1-rc2&signature&line=696
Trac metadata
Trac field | Value |
---|---|
Version | 8.2.1-rc2 |
Type | FeatureRequest |
TypeOfFailure | OtherFailure |
Priority | normal |
Resolution | Unresolved |
Component | Compiler |
Test case | |
Differential revisions | |
BlockedBy | |
Related | |
Blocking | |
CC | |
Operating system | |
Architecture |