I’ve always relied on loading the .mli files in the editor (Vim).
For a long time this was
:sfind bigarray.mli (with a path including ocaml source); with merlin it’s
:MLI bigarray, but after the stdlib restructuring, this particular invocation gives me an unhelpful stub including Stdlib.Bigarray.
I can see that the actual bigarray.mli is in a deeper nested directory in opam with the source. Adding that to my search path seems potentially fragile with version bumps. So I’ve just been working around the issue (opening the specific file) when it occurs.
And I guess the trigger to my asking about this now is the recent announcement of wonderful web-based module documentation. It makes me wonder: what do you do when your programming in OCaml and want to check documentation for a particular (installed) module?
I’m wondering if I’m missing out on something. Or, if others load local mli files as I do… how to nicely get the correct mli (and not a Stdlib stub). ie. When normal things don’t work… I begin to suspect what I’m doing isn’t normal anymore.