ocaml/dune

[Merlin] Curious Unbound module issue

Open

#12,611 opened on Oct 21, 2025

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)OCaml (478 forks)github user discovery
good first issuemerlin

Repository metrics

Stars
 (1,882 stars)
PR merge metrics
 (Avg merge 1d 20h) (345 merged PRs in 30d)

Description

I am running into quite a perplexing issue:

https://github.com/user-attachments/assets/04896779-1c65-438e-bc2f-d58bbe98243f

In essence, if I have a library lib and try to utilize it in an executable where there are multiple executables in the same folder and dune file, then the naming of the file will matter and the one utilizing the library will need to be first alphabetically?

I guess notably compilation with dune succeeds each time, but it seems the lsp is requiring something more?

Small example shown in screen recording: Durbatuluk1701/module_bug

Contributor guide

Research direction
Reproduce the issue using the provided example repository. Check the dune file configuration for the executable and library. Examine how file ordering affects module visibility in the LSP. Try different alphabetical orders to confirm the pattern.
Tech stack
None
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitOCamlDune
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60