aboutsummaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorsimonmar <unknown>2003-04-25 11:17:55 +0000
committersimonmar <unknown>2003-04-25 11:17:55 +0000
commitde886f789c38748bcad8ef0c8e518865c759f814 (patch)
tree45a6121d0f7360dc3d1da94e1b4a5b0eecc089d0 /TODO
parenteb12972c9b217d46397791c63d19c418b1a3c83f (diff)
[haddock @ 2003-04-25 11:17:55 by simonmar]
Some updates, including moving the derived instance item down to the bottom of the list now that Ross has contributed some code that does the job for common cases.
Diffstat (limited to 'TODO')
-rw-r--r--TODO27
1 files changed, 25 insertions, 2 deletions
diff --git a/TODO b/TODO
index 71e04c21..d4f57f7e 100644
--- a/TODO
+++ b/TODO
@@ -1,12 +1,11 @@
-----------------------------------------------------------------------------
-- bugs
+
* don't link to M.x if M.x is re-exported via a 'module N' from module M.
* Pick the preferred export names as per the paper.
-* instances: need to construct instances for deriving clauses, somehow.
-
* A module re-export should only reference the target module if the
target module is imported without hiding any of its exports (otherwise
we should inline just the exported bits).
@@ -23,9 +22,31 @@
* Document new labelling feature
+* For a module with no documentation section, include a "synopsis" header?
+
+* Parent button should be removed if there isn't a parent.
+
+* a paragraph like
+
+ > text
+ more text
+
+ is interpreted strangely: the second line is interpreted as part of the
+ code block, but the second line is non-literal (and markup within it
+ is interpreted normally). Rewrite the lexer using Alex, and fix this
+ at the same time.
+
+* derived instance support isn't quite right (doing it properly is
+ hard, though).
+
-----------------------------------------------------------------------------
-- features
+* merge the indices, adding annotations to distinguish types/classes/functions/
+ constructors as necessary.
+
+* nested itemized and enumerated lists.
+
* There ought to be a way to include some structure in the "description"
(section headings, etc.) and possibly in other comments. (suggseted
by Daan).
@@ -64,6 +85,8 @@
* Allow individual function arguments to be documented when the function
type is a record element?
+* hiding instances?
+
-----------------------------------------------------------------------------
-- cosmetic