> Lex why don't you try the following:
> 
> put a button that will recompute everything even if this takes long time and
> cache it.
>     -> this way we (the other users) will be able to play with it (and we
> will know that this is like that)
>     -> I think that in the beginning of a PhD you should know fast if the
> things you are doing are worth. that's why incremental changes are
> interesting but if you would have a solution for type inference that we
> could use for documentation this would be already great.
> 

Wow.  Well, if I find a spare 5 hours, I'll try and do it.  Time is
often tight, however....  Grad school easily sucks time away from
graduate work, oddly enough.



> I would really like from you if you could write in a wiki page all the
> information you would like to have in an AST for code analysis (and state if
> this is in Lucid).


This only takes 2 hours.  It's more likely.  :)



-Lex