I would like haddock to be aware of at least rudimentary package metadata. As as a start the package name of what is being build. The rationale for that is splitting the haddocks generated content page (the tree of modules) into a list of trees one per package. The simple way to solve this is to pass --package-name & --package-version to haddock which would be written to the interface file file; when haddock generates the content page it reads the interface files it would know which interfaces comes from which package:
I have a draft pr where I infer package names from interface file names.
I would like haddock to be aware of at least rudimentary package metadata. As as a start the package name of what is being build. The rationale for that is splitting the
haddocks
generated content page (the tree of modules) into a list of trees one per package. The simple way to solve this is to pass--package-name
&--package-version
to haddock which would be written to the interface file file; whenhaddock
generates the content page it reads the interface files it would know which interfaces comes from which package:I have a draft pr where I infer package names from interface file names.