chdir races when running ppx (#550).merlin files, and as a consequence no longer depends on dot-merlin-reader. (#523)Add a new code action Add missing rec keyword, which is available when adding a rec keyword can fix Unbound value ... error, e.g.,
let fact n = if n = 0 then 1 else n * fact (n - 1)
(* ^^^^ Unbound value fact *)Adding rec to the definition of fact will fix the problem. The new code action offers adding rec.
ocamlformat-rpc opam package to be installed. (#386)Add completion support for polymorphic variants, when it is possible to pin down the precise type. Examples (<|> stands for the cursor) when completion will work (#473)
Function application:
let foo (a: [`Alpha | `Beta]) = ()
foo `A<|>Type explicitly shown:
let a : [`Alpha | `Beta] = `B<|>Note: this is actually a bug fix, since we were ignoring the backtick when constructing the prefix for completion.
Construct command as completion suggestions, i.e., show complex expressions that could complete the typed hole. (#472)Construct an expression that is shown when the cursor is at the end of the typed hole, i.e., _|, where | is the cursor. The code action simply triggers the client (currently only VS Code is supported) to show completion suggestions. (#472)Code action to qualify ("put module name in identifiers") and unqualify ("remove module name from identifiers") module names in identifiers (#399)
Starting from:
open Unix
let times = Unix.times ()
let f x = x.Unix.tms_stime, x.Unix.tms_utimeCalling "remove module name from identifiers" with the cursor on the open statement will produce:
open Unix
let times = times ()
let f x = x.tms_stime, x.tms_utimeCalling "put module name in identifiers" will restore:
open Unix
let times = Unix.times ()
let f x = x.Unix.tms_stime, x.Unix.tms_utimeDo not show "random" documentation on hover
fixes duplicate:
Show typed holes as errors
Merlin has a concept of "typed holes" that are syntactically represented as _. Files that incorporate typed holes are not considered valid OCaml, but Merlin and OCaml-LSP support them. One example when such typed holes can occur is when on "destructs" a value, e.g., destructing (Some 1) will generate code match Some 1 with Some _ -> _ | None -> _. While the first underscore is a valid "match-all"/wildcard pattern, the rest of underscores are typed holes.
verbosity from 1 to 0. This is the same default that merlin uses. The old value for verbosity (#433)Get fresh diagnostics (warning and error messages) on a file save (#438)
Note: If you want the fresh diagnostics to take into account changes in other files, you likely need to rebuild your project. An easy way to get automatic rebuilds is to run dune in a watching mode, e.g.,[dune build --watch].
-short-paths even if the project wasn't built yetparams in a list. This is required by the spec. (#351)destruct as a code action in interface files (#255)