A New Era of OCaml Editing: Powered by Merlin, Delivered via LSP
summary
Merlin splits into Merlin Lib (compiler-facing core) and an LSP server so editors get completion, diagnostics and navigation without 1000 plugins while legacy clients keep Merlin for advanced workflows. Implementation targets VS Code and Neovim and already covers roughly 80% of typical IDE features; remaining Merlin-only capabilities use either collection (code actions) or custom request extensions per-editor. Work continues to upstream typing recovery into the compiler and to use multicore effects to parallelize incremental type checking.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:32OCaml tooling evolution and Merlin
- 3:24Editor plugin challenges
- 5:20Language Server Protocol adoption
- 8:33Merlin to LSP transition
- 10:31LSP with Merlin features
- 11:36Merlin split into Lib and servers
- 13:24LSP advantages for OCaml
- 15:56Future parity and extensions
- 17:21Custom requests vs code actions
- 21:59Implementation progress
- 23:50Ongoing work and performance
- 25:57Conclusion and Q&A
