What is a good way to enumerate definitions (implementations) of a compilation unit (module file)? For disambiguation purpose the right type of function is
Env.find_value: Path.t -> t -> value_description if a path is given. However I would like to enumerate all the paths that define values in a structure (and its sub-modules). Additionally it would be nice to know how to generate a subset of paths (those available through the interface) from the
Motivation: this is equivalent to providing a tag file that lets you “jump to definition”. Currently from
Typedtree API (.cmt file) I can generate a reference but external reference points to the
val_loc in the signature file. I would like to be able to point to the implementation as well.