it would be really cool if I could write all of kaslisp‘s interpreter’s unit-tests in kaslisp itself

the only problem is, in order to do that I would have to figure out how to print the line number that the error came from. otherwise the error message would amount to “something broke lol”

maybe I could find a way to print the S-expression that failed? hmm

anyway I’ve been writing this thing in a haze of sleep deprivation so I’m adding unit-tests to tell me if/when I break everything. and they work! 3 of them failed so I broke 3 things that I know of. I’ll fix them later

also I’m doing really cursed metaprogramming: you can actually run regular Python functions from inside of kaslisp, because I’m able to introspect about what arguments a Python function expects. every kaslisp function that isn’t a special form and isn’t defined in kaslisp itself is going to be a Python function

(or, that’s the idea anyway. I haven’t tested it yet)