Update TODO notes.
Chris Pressey
6 years ago
49 | 49 | |
50 | 50 | ### TODO |
51 | 51 | |
52 | * (+) Consider what it would take to add a predicate that evaluates to whether | |
53 | a given action has been taken previously or not. | |
54 | * (+) Consider macros. | |
55 | 52 | * Output scenarios to JSON. |
56 | * Consider a simple equality rule. | |
57 | * Consider allowing `∨`. | |
58 | 53 | * Take AST code from SixtyPical or ALPACA (or try to do better, perhaps with |
59 | 54 | named tuples, but this is probably madness and not at all worth doing) |
60 | 55 | |
61 | #### Probably we don't do | |
56 | ### TODO for v0.3 | |
62 | 57 | |
63 | * (+) Allow sentence trees to be given for actions. | |
64 | * (+) Allow scenarios to specify a minimum number of events to generate. | |
58 | * Consider what it would take to add a predicate that evaluates to whether | |
59 | a given action has been taken previously or not. | |
60 | * Consider macros. | |
61 | * Consider a simple equality rule, `eq(?X,?X)` but built-in. | |
62 | * Consider a "wildcard" variable that will match anything *without* binding it. | |
63 | * Consider making "wildcard" work such that you can say `¬holding(?_, club)` | |
64 | to mean "if no one is holding the club". |