New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Haddock always shows kind signatures for types re-exported from other packages #548
Comments
The reason for this problem is probably because Haddock is reverse engineering the source declaration from the recorded type in the GHC interface file, and then forgetting to suppress kinds (when you have it directly, it just uses the renamed source directly.) |
alexbiehl
pushed a commit
to alexbiehl/haddock
that referenced
this issue
Feb 1, 2018
alexbiehl
pushed a commit
that referenced
this issue
Feb 1, 2018
sjakobi
pushed a commit
to sjakobi/haddock
that referenced
this issue
Jun 10, 2018
(cherry picked from commit 60e10eb)
bgamari
added a commit
to bgamari/haddock
that referenced
this issue
Jun 14, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I run haddock on the following modules
the types are formatted as expected, without kind-signatures.
However, if I move
Foo
into a separate package it suddenly has a kind-signature in theBar
haddocks.It would be nice if haddock would only display kind signatures when one of the type parameters has a non-
*
kind, otherwise it's just noise IMO.The text was updated successfully, but these errors were encountered: