summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorOskar <[email protected]>2024-03-27 20:14:19 +0100
committerOskar <[email protected]>2024-03-27 20:14:19 +0100
commite19ac11ab4136d7950ca8e55dbc028d77c5925a7 (patch)
treea6f8ec8f534615eca1e352325f64122ae0b978ed /TODO
parent6e257dde5283da748df7fe619aeadaea1f7c1f18 (diff)
parent90bae0258e609631270148d3883cffa472bab006 (diff)
Merge branch 'validate-L'
Diffstat (limited to 'TODO')
-rw-r--r--TODO10
1 files changed, 6 insertions, 4 deletions
diff --git a/TODO b/TODO
index 23f9e21..d57d53d 100644
--- a/TODO
+++ b/TODO
@@ -1,7 +1,9 @@
TODO list. This is mostly so i can plan more granularly and remember small stuff i was working on last time and what i should prioritise first.
This is not my overall big planning board. (1 highest prio, 10 lowest)
-1 - implement validate_imm_numbers
-1 - test validate_imm_numbers
-1 - testcases for the function above
-2 - re-implement validate_L
+1 - Write testcases for validate_L
+1 - Perform some tests on validate_L
+2 - Have a big long think about how validate_N should work
+2 - implement validate_N
+2 - Perform tests on validate_N
+3 - Have a big long think about how the strings will be processed and translate in to actually doing things in the program.