Stack Version 2.16.0, Git revision 0f8087c0dfb906f5bb514aa87b88cdd68b5b52f1 (10650 commits) PRE-RELEASE x86_64 has --haddock-executables but the links in the combined documentation do not work. That is because of the following:
Cabal (the library) haddock --executables creates Haddock documentation for components in subdirectories (named after the component) of the directory used for the main library Haddock documentation;
that Haddock documentation has links in the form ../<package-identifier>/;
so, when the combined Haddock documentation is formed, those subdirectories need to be 'lifted up' to be on the same level as the directories of Haddock documentation for libraries.
It seems to me that the 'lifting up' should not be too complex. However, some thought will need to be given the possibility of name clashes. In that regard, I think that components like executables, test suites and benchmarks depend on libraries and not vice versa.
Stack Version 2.16.0, Git revision 0f8087c0dfb906f5bb514aa87b88cdd68b5b52f1 (10650 commits) PRE-RELEASE x86_64 has
--haddock-executablesbut the links in the combined documentation do not work. That is because of the following:haddock --executablescreates Haddock documentation for components in subdirectories (named after the component) of the directory used for the main library Haddock documentation;../<package-identifier>/;It seems to me that the 'lifting up' should not be too complex. However, some thought will need to be given the possibility of name clashes. In that regard, I think that components like executables, test suites and benchmarks depend on libraries and not vice versa.
Sublibraries are, in practice, not an issue at the moment because they are broken with Cabal (the library): https://github.com/haskell/cabal/issues/9586