aboutsummaryrefslogtreecommitdiff
path: root/Tasks.org
diff options
context:
space:
mode:
authorAria <me@aria.rip>2023-10-24 19:34:06 +0100
committerAria <me@aria.rip>2023-10-24 19:34:06 +0100
commit6ab23435a79f8e95358e1a69ccec58e809420449 (patch)
treee17ef77a59028ced518b9e79c142660b1e5fc1b4 /Tasks.org
parentf367ebb3764991956f84573bfad3f6657e4b5e54 (diff)
chore: update tasks
Diffstat (limited to 'Tasks.org')
-rw-r--r--Tasks.org6
1 files changed, 4 insertions, 2 deletions
diff --git a/Tasks.org b/Tasks.org
index 3e4c1a3..0abdcb3 100644
--- a/Tasks.org
+++ b/Tasks.org
@@ -33,9 +33,11 @@ We also need to know where we can find the implementation types, for use in buil
This will involve exposing interfaces for the library specifications, candidate generation, and code generation.
We can also take this as an opportunity to make it slightly more robust and well-documented, although this is a secondary goal.
-** TODO Interface for implementation library
+** DOING Interface for implementation library
-We should be able to list every implementation available, and its module path.
+We can list every implementation available, its module path, the traits it implements, and a bunch of generated racket code.
+
+Next we should also be able to turn the list of implemented traits into a list of operations.
** TODO Interface for candidate generation