_____________________________________________________________________________
Immediately
- - I still don't like Atom.Infer and Atom.Invert...
+ - The repeat API's in Sequence are ugly
+ - segregate the sequence static-constructors?
- - better ambiguity debugging tools
+ - Sequence shouldn't be an Element -> make Union.add(Element)
+ - Should Tree<T> really be type-parameterized?
+ - do Forest/Tree still need a Region?
- - ParseFailed, GSS, Walk, Parser, Sequence, Forest
+ - reconsider the degree of genericization
+
+ - grammar highlighting?
+ - comment indentation vs block indentation?
+ - { and } in <pre>
+ - recursive { { foo } }
- - Fix the metagrammar (really?)
- - evil problems with (x y? z /ws)
+ - More topology untangling
+ - Forest needs a "manual access" API
+ - the unwrap bit in Forest makes it really hard to expose an API for forests
+ - evil problems with (x y? z /ws)
+ - ParseFailed, GSS, Walk, Parser, Sequence, Forest
- copyright notices
- documentation
+
______________________________________________________________________________
v1.1
- RFC2822 (email message/headers)
- clean up the whole Walk situation (?)
- - what if Tree<> could unwrap itself?
-
______________________________________________________________________________
Soon
- eliminated statically?
- substring parsing for better error messages
- - "lift" cases:
- - right now I can only lift the last child in a forest... begs
- the question of what the right representation for Forests is
- if we need to be able to do lift operations on it.
- Parameterized LR
- "Regular Right Part" grammars (NP Chapman, etc)