It's perfectly valid to have a dune project containing sub-libraries that have unwrapped modules with the same name. For example:
one/names.ml
two/names.ml
Where the public-name for these is e.g. repro.one and repro.two. These libraries can't be linked together, but the documentation should be able to coexist. Currently this is not possible as odoc is producing the same html filename for both modules:
Multiple rules generated for _build/default/_doc/_html/repro/Names/index.html:
- <internal location>
- <internal location>
It's perfectly valid to have a dune project containing sub-libraries that have unwrapped modules with the same name. For example:
Where the public-name for these is e.g.
repro.oneandrepro.two. These libraries can't be linked together, but the documentation should be able to coexist. Currently this is not possible as odoc is producing the same html filename for both modules: