diff options
author | ubq323 <ubq323@ubq323.website> | 2024-07-02 17:17:01 +0100 |
---|---|---|
committer | ubq323 <ubq323@ubq323.website> | 2024-07-02 17:17:01 +0100 |
commit | 033a9cbb66d65a0918e2c095d12937afb82fd4b2 (patch) | |
tree | 29d5314ff15aa677b732d2631d555c2a6b1d942d /todo | |
parent | 6e8123763241efcb259f68d6e0e6d3ffcbc32795 (diff) |
add (each (x arr) ...) array-loop form
Diffstat (limited to 'todo')
-rw-r--r-- | todo | 81 |
1 files changed, 46 insertions, 35 deletions
@@ -1,38 +1,49 @@ -closures, upvalues -good repl -arrays, hashes, other useful types - arrays: - get index - set index - get length - literals - append - concat - conformation of at least arithmetic over arrays - hashes: - get index - set index - get count - literals - merge? - delete? - should probably implement ht with keys other than strings - user-defined structs, somehow, maybe -good loops - numeric for - array for each - functional variants of the above - variants of the above that record an array of all their results -pattern matching +[_] closures, upvalues + +[_] good repl + +[_] arrays, hashes, other useful types + [_] arrays: + [x] get index + [x] set index + [x] get length + [x] literals + [x] append + [_] concat + [_] conformation of at least arithmetic over arrays + [_] hashes: + [_] get index + [_] set index + [_] get count + [_] literals + [_] merge? + [_] delete? + [_] keys other than strings + + [_] user-defined structs, somehow, maybe + +[_] good loops + [x] numeric for + [x] array for each + [_] really these both should be macros or something + [_] functional variants of the above + [_] variants of the above that record an array of all their results + +[_] pattern matching probably doesn't need to be too complex -garbage collector - go thru everything make sure references are kept around properly -macros -error handling - record line and col of everything + +[_] garbage collector + [_] go thru everything make sure references are kept around properly + +[_] macros + +[_] error handling + [_] record line and col of everything not sure how to do error handling in language but at least - make the error messages good - more sophisticated testing of errors + [_] make the error messages good + [_] tracebacks etc + [_] more sophisticated testing of errors instead of just literally matching error message -tidy and clean the code - properly do bounds checking everywhere etc + +[_] tidy and clean the code + [_] properly do bounds checking everywhere etc |