Hi Claus,
> While you're revisiting Hoogle, might you be able to
> work from .haddock and .hi files (via haddock API and
> GHC API/ghci), instead of from sources, making Hoogle
> independent of/separate from Haddock's frontend?
All Hoogle needs is a way to generate a text file listing exactly
wha
I'm revisiting Hoogle development and the base library is the one
sticking point before I make a new Hoogle release.
While you're revisiting Hoogle, might you be able to
work from .haddock and .hi files (via haddock API and
GHC API/ghci), instead of from sources, making Hoogle
independent of/se
Hi,
For nearly all packages on hackage, haddock is run over them with
--hoogle, which generates documentation
(http://hackage.haskell.org/package/stm) and a hoogle database
(http://hackage.haskell.org/packages/archive/stm/2.2.0.1/doc/html/stm.txt).
However, the base library is special, and hackage
