Hi Jan,
The commentary is a great place to start to understand the GHC pipeline. In
fact, GHC is an incredibly well documented project. However, being a place
where a lot of new theory gets tested, its' also one of the densest and
most intimidating (It's perhaps the only source code I've read
And this is where I'm a little stuck too. I have a reasonably good
picture
of GHC's pipeline, having worked on it for my master's thesis, and I'd
like
to get more involved and possibly even contribute something useful. But
I'm
not sure where to start.
Well, that's a bit discouraging -
On Thu, Dec 13, 2012 at 12:56 PM, Jan Stolarek jan.stola...@p.lodz.plwrote:
Speaking of your thesis - have you worked out internals of GHC by yourself
or did you have someone
with knowledge of GHC supervise your work?
I worked on my own, but the GHC folk were very helpful when I got stuck.
Hello,
Is there a way to get access to the STG syntax tree of a program using
the GHC api? i.e. a function that returns something of type `StgExpr'
that can be used in a way similar to this:
example module =
defaultErrorHandler defaultDynFlags $ do
runGhc (Just libdir) $ do
