You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I've recently joined the Jane Street compiler team. We've had a user report a bug, which I've included reproduction steps for below. Essentially, there is an import.ml file, which includes another module named Import. This leads to a Import.Import module existing in scope. When another file contains open Import, Merlin traces the location of Import to the correct location when the file is a .ml file but incorrectly traces to Import.Import when the file is a .mli file.
Hi, I've recently joined the Jane Street compiler team. We've had a user report a bug, which I've included reproduction steps for below. Essentially, there is an
import.ml
file, which includes another module namedImport
. This leads to aImport.Import
module existing in scope. When another file containsopen Import
, Merlin traces the location ofImport
to the correct location when the file is a.ml
file but incorrectly traces toImport.Import
when the file is a.mli file
.Reproduction Steps
cd
into thejump_to_wrong_import
directorydune build
ocamlmerlin single locate -position 1:10 -look-for implementation -filename lib/foo.mli < lib/foo.mli
This gives:
Compare this to
ocamlmerlin single locate -position 1:10 -look-for implementation -filename lib/foo.ml < lib/foo.ml
, which gives the expected:Version info:
ocamlmerlin
built from d5dd40e70eceabe7f9c7c413141430e57e44ded4 (up-to-date master as of the time of posting this)dune
3.14.2ocaml
4.14.2Full opam env:
The text was updated successfully, but these errors were encountered: