Hi,
I noticed some time ago the fact that qualified imports doesn't affect the
generated documentation.
It's kind of clumsy in case of libraries that define a lot of synonyms
(vector and bytestring come in my mind first).
For instance, in the package utf8-string:
2011/12/6 Yves Parès limestr...@gmail.com:
Hi,
I noticed some time ago the fact that qualified imports doesn't affect the
generated documentation.
It's kind of clumsy in case of libraries that define a lot of synonyms
(vector and bytestring come in my mind first).
For instance, in the
I'll try that.
But if it does this, why isn't the documentation on hackage generated with
that option?
(Sorry, I was mostly talking about it, since I don't always install
documentation locally, I check it on hackage)
2011/12/6 David Waern david.wa...@gmail.com
2011/12/6 Yves Parès
2011/12/6 David Waern david.wa...@gmail.com:
2011/12/6 Yves Parès limestr...@gmail.com:
It should be written that this 'ByteString' is not a newly defined type but
instead a re-exportation.
It should be simple to add some kind of Re-export of link to
original thing tag to the Haddock
I've long wanted a display it like I typed it option, e.g. if I
typed 'Module.function' the link would look exactly like that.
I've also often wished that unimported but fully qualified modules
like 'Data.List.partition' would link even if Data.List is not
imported. I suppose similarly to the
2011/12/6 Evan Laforge qdun...@gmail.com:
I've also often wished that unimported but fully qualified modules
like 'Data.List.partition' would link even if Data.List is not
imported. I suppose similarly to the way that s blind link
without having to know about the module in question.
That's
On Tue, Dec 6, 2011 at 11:51 AM, David Waern david.wa...@gmail.com wrote:
2011/12/6 Evan Laforge qdun...@gmail.com:
I've also often wished that unimported but fully qualified modules
like 'Data.List.partition' would link even if Data.List is not
imported. I suppose similarly to the way that s
