Simon Marlow wrote:
>
> No, it doesn't work like that because we wouldn't get enough
> parallelism.  Dependencies are tracked at the module level, so the
> dependency graph that make sees contains all modules of all libraries,
> including GHC itself.  The Build-depends line is used to ensure that we
> configure packages in the correct order.
>
> Unfortunately Template Haskell (and hence annotations) breaks this idea,
> because TH needs the whole package compiled in order to load it.  This
> fragment from ghc.mk might be illuminating:

Should we just abandon TH in DPH and use something else to generate our
boilerplate? We could also use something other than annotations for
configuring SpecConstr. It really seems to be more trouble than it's worth
to me. It's not the first time we've run into problems with TH.

Roman




_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to