aboutsummaryrefslogtreecommitdiff
path: root/Tasks.org
diff options
context:
space:
mode:
authorAria <me@aria.rip>2023-10-26 12:42:21 +0100
committerAria <me@aria.rip>2023-10-26 12:42:21 +0100
commit956ed5a821a7d04d8c54e21a7f4a6dece70bc9a3 (patch)
tree1caf3653e4a22da9101671b3036a9add0eab8064 /Tasks.org
parent6ab23435a79f8e95358e1a69ccec58e809420449 (diff)
chore: update tasks
Diffstat (limited to 'Tasks.org')
-rw-r--r--Tasks.org6
1 files changed, 3 insertions, 3 deletions
diff --git a/Tasks.org b/Tasks.org
index 0abdcb3..c12bb1f 100644
--- a/Tasks.org
+++ b/Tasks.org
@@ -33,13 +33,13 @@ 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.
-** DOING Interface for implementation library
+** DONE Interface for implementation library
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.
+We don't need a list of operations right now, as we'll just make a seperate implementation of cost model building for each trait, and that will give us it.
-** TODO Interface for candidate generation
+** DOING Interface for candidate generation
We should be able to get a list of candidates for a given file, which links up with the implementation library correctly.