The documentation has some funny links. If you click on the Builder in the type of serialiseIncremental, for example, it will take you to documentation for Data.Binary.Builder.
My best guess: Haddock sees that Builder is exported by Data.ByteString.Lazy.Internal (which is imported by Codec.Serialise). It recognizes that D.B.L.Internal is hidden from Haddock, and goes in search of an appropriate target. Somehow (and I really have no idea how) it selects binary.
hvr
commented
7 years ago
The documentation has some funny links. If you click on the
Builderin the type ofserialiseIncremental, for example, it will take you to documentation forData.Binary.Builder.My best guess: Haddock sees that
Builderis exported byData.ByteString.Lazy.Internal(which is imported byCodec.Serialise). It recognizes thatD.B.L.Internalis hidden from Haddock, and goes in search of an appropriate target. Somehow (and I really have no idea how) it selectsbinary.