Custom Query (117 matches)
Results (28 - 30 of 117)
|#1562||fixed||darcs-based wiki engine||davidlazar|
A darcs-driven wiki engine.
|#1565||fixed||Build a package API tool||simonmar|
We need a tool that does the following:
It could be built on top of the GHC API fairly easily. This would make a great SoC project, I think - it has few dependencies, and if the student finishes the basic functionality early, there's lots more that could be added to it, for example Cabal/Hackage? integration.
This is a very useful project from the point of view of making Hackage more robust. More packages following the PVP and correctly specified dependencies will mean much more reliable package management for the whole Haskell community.
There is an existing tool that could serve as a basis for the project:
It appears to have seen no new development since it was posted in Nov 2009.
A relevant ticket in Haddock:
In general it would be good to consider what other projects need in this area, for example Hoogle, and see whether any universally useful infrastructure could be built.
|#1567||fixed||Haddock: allow documentation to propagate between packages||simonmar|
Haddock is not able to document entities that are re-exported from a module in another pacakge. This has been a long-standing problem with Haddock, and is the reason that some of our documentation looks a bit strange (e.g. the List module).
In order to fix this, we need to serialise declarations and documentation in Haddock's .haddock files. A lot of binary instances need to be written.
Here's the Haddock ticket: