From 29b18bc1de689f9339f82a9ceb30cad5157b7f56 Mon Sep 17 00:00:00 2001 From: Aryadev Chavali Date: Thu, 21 Aug 2025 14:56:07 +0100 Subject: Finish value constructors TODO, start container constructors TODO --- alisp.org | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'alisp.org') diff --git a/alisp.org b/alisp.org index 542e4eb..45e7432 100644 --- a/alisp.org +++ b/alisp.org @@ -42,15 +42,13 @@ perspective. Should we capitalise symbols? This way, we limit the symbol table's possible options a bit (potentially we could design a better hashing algorithm?) and it would be kinda like an actual Lisp. -** DONE Test value constructors and destructors :test: -Test if ~make_int~ works with ~as_int,~ ~intern~ with ~as_sym~. -Latter will require a symbol table. -** TODO Test containers constructors and destructors :test: +** WIP Test containers constructors and destructors :test: Test if ~make_vec~ works with ~as_vec~, ~cons~ with ~as_cons~ AND ~CAR~, ~CDR~. -We may need to think of effective ways to deal with NILs. Maybe make -functions as well as the macros so I can choose between them? +We may need to think of effective ways to deal with NILs in ~car~ and +~cdr~. Maybe make functions as well as the macros so I can choose +between them? ** TODO Test system registration of allocated units :test: In particular, does clean up work as we expect? Do we have situations where we may double free or not clean up something we should've? @@ -110,3 +108,6 @@ Latter approach time complexity: Former approach is better time complexity wise, but latter is way better in terms of simplicity of code. Must deliberate. +** DONE Test value constructors and destructors :test: +Test if ~make_int~ works with ~as_int,~ ~intern~ with ~as_sym~. +Latter will require a symbol table. -- cgit v1.2.3-13-gbd6f