Haddock version during build
david.waern at gmail.com
Fri Jun 13 12:16:40 EDT 2008
2008/6/13 Ian Lynagh <igloo at earth.li>:
> We can do this, but I think we should be careful about which library we
> choose. There are a number of libraries doing this sort of thing, and we
> don't want 3 different parts of the GHC bundle to end up using 3
> different ones for no good reason.
> If I remember correctly, Neil's only really works with a single
> datatype, and I'm therefore not sure it would be a good match for GHC's
> mutually recursive datatypes.
You are probably confusing derive with uniplate, which is a library
for generic traversals. The derive package is about automatic instance
derivation. But you're right that we'd have to choose a traversal
library, out of several available ones. I thought Data.Traversable
would be a good choice since it's already in the boot libraries.
> Another thing to think about is these bugs:
> about giving docs for things reexported from another package. One way to
> fix this would be for GHC to put the doc info in the .hi file (or
> another auxiliary file); I think GHC can already parse the info?
Yes, although putting the doc info in the .haddock file would also work.
More information about the Cvs-libraries