Unbound module for library if library name the same as test name

[jakzale]

Problem

If the name of a test/executable in dune is the same as its library dependency, then ocamllsp will report Unbound module for that library, but dune build, dune runtest, or dune exec will work just fine.

Unfortunately, dune init project <name> uses a template with the same name for library and a test, which potentially can lead to confusion for newcomers.

Versions

ocaml 4.14.0
dune 3.3.1
ocamllsp 1.12.2

Tested in Visual Studio Code 1.69.0, using OCaml Platform v1.10.7.

Steps to Reproduce

1. Create a project from dune's default template

$ touch dune-workspace
$ dune init project example
Success: initialized project component named example
$ dune build

2. Create a module in the library

Put the following in example/lib/foo.ml:

let foo () =
  print_endline "Hello, world!"

3. Use the module in a test

Update example/test/dune to following:

(test
 (name example)
 (libraries example))

Update example/test/example.ml to following

let () =
  Example.Foo.foo ()

4. Run tests

$ dune runtest
Hello, world!

Bug?

Even though dune runtest works fine, ocamllsp reports Unbound module Example in example/test/example.ml:

Potential Workaround

Renaming the test to a different (i.e. test_example) by changing the name field in example/test/dune:

(test
 (name test_example)
 (libraries example))

and changing the name of the file

$ git mv example/test/example.ml example/test/test_example.ml

Fixes the problem.

[jbulow]

This still seems to be a problem. Should the dune init template be updated or should it be documented somewhere?

It is a bit confusing with the current situation when the init template is broken.