4 ms·
> when signatures changed in an unstable dependency The problem is not OCaml here.
by shikoba 4y ago
> when signatures changed in an unstable dependency
The problem is not OCaml here.
- muglug 4y agoI have a good point of contrast: I'm doing a similar task with an unstable Rust dependency, and when APIs change the error messages from the typechecker are crystal clear about why things are incompatible.
- shikoba 4y agoI see, you made the beginner mistake with OCaml. You should never read the OCaml error message except if all other options failed. Try to not read those messages, but just look at the line where the error occured. You can use -annot or -bin-annot when compiling and the Tuareg function caml-types-show-type in Emacs will be your best friend.
- c-cube 4y agoThis is old advice :-). Use the LSP server and dune and the error displays instantly, no further setup required.
- shikoba 4y agoI don't get it. Is it sarcasm?
- wiseowise 4y agoNo. You don't need this anymore. > You can use -annot or -bin-annot when compiling and the Tuareg function caml-types-show-type in Emacs will be your best friend. Just open OCaml program in some editor with LSP(Vim, NeoVim, VS Code, Emacs) and it will instantly show you the error.
- shikoba 4y agoThat's sad. I need dune to make it work.
- yawaramin 4y agoDune has its quirks but it's pretty good at its job. The community is standardizing on it and every time someone pops up on the forum asking for help with weird issues because they didn't use dune, I think they're just making thing hard on themselves for very little benefit.
- fspeech 4y agoHe is just recommending the use of LSP server, which requires little to no configuration and works with any editor/IDE.
- BiteCode_dev 4y agoYes because we all work in perfect world under optimal conditions.