Open guibou opened 1 year ago
Tried with haddock
with ghc 9.0.2
Could it be that this bug affects re-exports in a more general way? I have something like:
import Data.Attoparsec.ByteString.Char8
fooP :: Parser a
...
and haddock reports
could not find link destinations for:
- Data.Attoparsec.ByteString.Internal.Parser
but Parser
is re-exported by Data.Attoparsec.ByteString.Char8
.
In my module, I'm importing
Data.Text.Text
and using it in a function signature.However, my library depends on
text
andfoldl
andfoldl
reexportsText
in theControl.Foldl.Text
module.Even if I'm not importing
Control.Foldl.Text
in my module, haddock generates links documentation to this module instead of a link to theData.Text.Text
module.For exemple:
I've created a new library with
cabal init
which contains this file:Note: this is the default library generated by
cabal init
with the added (and exported)fiz
symbol.Note that it imports the
Data.Text
module.If I only depend on
text
on mycabal
file, the generated haddock correctly points toData.Text.Text
. However, if I'm addingfoldl
in mycabal
file, the generated documentation points toControl.Foldl.Text
, as you can see here:Changing the order of the dependencies in the
cabal
file does not change the result.