re-use merlin process or more complete ocaml pkg?

[hnry]

Hi nice project, easy to get up and running.

Currently if a merlin process is already spawned, this pkg will spawn it's own regardless. I don't know if merlin supports multiple environment contexts. If it does then re-using a existing process should be the right way to go.

The issue of multiple merlin processes comes up if we are using the autocomplete package (from facebook/nuclide) and this pkg.

And I do believe both do get used together quite frequently for those using ocaml with atom because one package provides autocompletion but does not provide warnings or errors. And the opposite is true for your pkg.

Ideally there would be one package that provides both, since both are using merlin. So if you have the time to also include autocomplete, then people can just drop nuclide entirely.

And for linting, I believe ocp-indent should probably be used there.

But anyway, these are just thoughts, I am glad ocaml is useable for atom with nuclide + your package. Just think they don't deserve to be separated into 2 pkgs 😝

[eriklovlie]

Thanks for the feedback! I've been wanting to extend the package so it provides autocompletion and go-to-definition. Should be simple in theory but I'm not sure when I have the time.

[eriklovlie]

Looks like the nuclide package now provides ocaml linting, afaict from browsing the github repo. So that's good, I hope facebook puts more work into the ocaml part of nuclide.

When I started this package it looked a lot like nuclide was not going to focus on ocaml (but instead on "web and mobile development" as they state in the description) and only provided a couple of nice-to-have things. For me it is still nice to have a package that doesn't care about anything else than ocaml, since that's fewer dependencies (e.g. none of this hack-lang stuff like watchman etc).

Let's wait and see I guess. Meanwhile I'll probably work on adding the rest of the good stuff merlin provides (autocomplete, etc).