should haddock.ghc be a sub-repo of ghc?

[David Waern]

> | In the meantime we could consider the less invasive change: put
> FastString
> | in place of HsDoc in HsSyn.  No need to pass functions into GHC to do
> the
> | renaming: Haddock can do it itself since it only needs the top-level
> | GlobalRdrEnv which GHC provides.  I don't think Haddock needs HsSyn with
> | parsed/renamed documentation embeded, since it can keep the
> documentation
> | in a Name->Doc mapping after it has extracted and processed it.  Sound
> | reasonable?
>
> That sounds reasonable to me.
>
> S

Me too. But what happens if we in the future get the comments from the .hi
files and don't bother with typechecking? Can we then reconstruct the
GlobalRdrEnv easily? I guess the exported names from each .hi file should
suffice, but I don't know the details of renaming.

David