oreodave/alisp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

alisp.org: mark some TODOs

Browse Source
This commit is contained in:
Aryadev Chavali
2026-02-11 08:04:13 +00:00
committed by oreodave
parent 2dc0c6080e
commit d88bc2baeb
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
alisp.org
View File

@@ -45,11 +45,13 @@ i.e. no parsing.
*** DONE Design what a "parser function" would look like *** DONE Design what a "parser function" would look like
The general function is something like ~stream -> T | Err~. What The general function is something like ~stream -> T | Err~. What
other state do we need to encode? other state do we need to encode?
*** TODO Write a parser for integers *** WIP Write a parser for integers
*** TODO Write a parser for symbols *** DONE Write a parser for symbols
*** TODO Write a parser for lists *** DONE Write a parser for lists
*** TODO Write a parser for strings
Requires [[*Design Strings for the Lisp]] to be complete first.
*** TODO Write a parser for vectors *** TODO Write a parser for vectors
*** TODO Write the general parser *** WIP Write the general parser
** Unit tests :tests: ** Unit tests :tests:
*** TODO Test streams *** TODO Test streams
**** DONE Test file init **** DONE Test file init
@@ -109,12 +111,12 @@ Super obvious.
*** TODO Design Strings for the Lisp :api: *** TODO Design Strings for the Lisp :api:
We have ~sv_t~ so our basic C API is done. We just need pluggable We have ~sv_t~ so our basic C API is done. We just need pluggable
functions to construct and deconstruct strings as lisps. functions to construct and deconstruct strings as lisps.
** Backlog ** Design :design:
*** TODO Design Big Integers :api: *** TODO Design Big Integers :api:
We currently have 62 bit integers implemented via immediate values We currently have 62 bit integers implemented via immediate values
embedded in a pointer. We need to be able to support even _bigger_ embedded in a pointer. We need to be able to support even _bigger_
integers. How do we do this? integers. How do we do this?
*** TODO Design garbage collection scheme :design:gc: *** TODO Design garbage collection scheme :gc:
Really, regardless of what I do, we need to have some kind of garbage Really, regardless of what I do, we need to have some kind of garbage
collection header on whatever managed objects we allocate. collection header on whatever managed objects we allocate.