Chile`: kowey: just a general hacking request, but its amazingly helpful to have
a tree heirarchy of parts/behaviors/functions along with where specifically
they're implemented & maybe briefly what other parts they touch

Chile`: kowey: the big hurdle is getting familiar with the code base, which
isn't worth it for most people for a patch or two, especially if they're not
sure what mucking with one thing will do to another

Very true. Using my time machine, I've made a start on this. Please give
tools/index.hs and make overview from
http://article.gmane.org/gmane.comp.version-control.darcs.user/12731 a try.

Simon's tools/index.html and make overview are now gone, but I'm not sure that
an automated solution to this request is even possible.

We've started collecting stuff here http://wiki.darcs.net/DarcsInternals and we
now have haddock at http://darcs.net

What else can we do?

I think I'm going to wont-fix this unless somebody can shed light on the request
or take charge of the code documentation initiative :-(

graphtype has just been released; it generates nice diagrams of types. It worked 
well on smaller programs I tried, but fails to parse something in the darcs 
source. If that could be worked around, it would probably generate valuable 
visualisations.

It seems to choke on CPP flags; specifically, 
[05:16 PM] 0Mb$ graphtype `find . -name "*.lhs"` `find . -name "*.hs"`
./src/unit.lhs: 74: 1
Parse error: VarSym "#"

(Which seems to be due to '#include impossible.h')

As it uses haskell-src-exts, and hlint uses haskell-src-exts but handles CPP
fine, I think this is just a bug in graphtype. Has anyone contacted the author?