I'll try that.<br>But if it does this, why isn't the documentation on hackage generated with that option?<br>(Sorry, I was mostly talking about it, since I don't always install documentation locally, I check it on hackage)<br>
<br><div class="gmail_quote">2011/12/6 David Waern <span dir="ltr"><<a href="mailto:david.waern@gmail.com">david.waern@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2011/12/6 Yves Parès <<a href="mailto:limestrael@gmail.com">limestrael@gmail.com</a>>:<br>
<div class="im">> Hi,<br>
><br>
> I noticed some time ago the fact that qualified imports doesn't affect the<br>
> generated documentation.<br>
> It's kind of clumsy in case of libraries that define a lot of synonyms<br>
> (vector and bytestring come in my mind first).<br>
> For instance, in the package utf8-string:<br>
> <a href="http://hackage.haskell.org/packages/archive/utf8-string/0.3.7/doc/html/Data-ByteString-UTF8.html" target="_blank">http://hackage.haskell.org/packages/archive/utf8-string/0.3.7/doc/html/Data-ByteString-UTF8.html</a><br>
><br>
> Here, the documentation doesn't say that the<br>
> utf8-string/Data.ByteString.UTF8.ByteString datatype used all along comes in<br>
> fact from Data.ByteString.<br>
> If it were instead a new implementation of ByteString (as for<br>
> bytestring/Data.ByteString.Char8.ByteString) the documentation would look<br>
> exactly the same, so to disambiguate to reader has to crawl through the code<br>
> to get to the initial definition.<br>
> (clicking on a 'ByteString' doesn't even redirect you to the original<br>
> bytestring/Data.ByteString page)<br>
><br>
> It should be written that this 'ByteString' is not a newly defined type but<br>
> instead a re-exportation.<br>
<br>
</div>It should be simple to add some kind of "Re-export of <link to<br>
original thing>" tag to the Haddock documentation. Feel free to add a<br>
ticket for this feature to the issue tracker<br>
(<a href="http://trac.haskell.org/haddock" target="_blank">trac.haskell.org/haddock</a>) with a description of how it should work.<br>
<div class="im"><br>
> It's even worse when you see the doc of a module that uses in the meantime<br>
> lazy and strict ByteStrings, or normal and unboxed/storable/<insert flavour<br>
> here> vector: you have to hover the type name to see which haddock page it<br>
> points to.<br>
><br>
> In that case, a solution might be to indicate on top of the doc page that it<br>
> uses another module as a qualified import, and to keep the prefixes in the<br>
> function signatures.<br>
<br>
</div>Maybe. But have you tried experimenting with Haddock's --qual flag?<br>
<span class="HOEnZb"><font color="#888888"><br>
David<br>
</font></span></blockquote></div><br>