beartype VS ulisp

https://github.com/beartype/beartype

I wish more people started using Beartype, it makes Python bearable

I saw this on /r/Python the other day...

As other folks have commented, type hints are now a big deal. For static typing the best checker is pyright. For runtime checking there is typeguard and beartype. These can be integrated with array libraries through jaxtyping. (Which also works for PyTorch/numpy/etc., despite the name.)

Maybe you're looking for https://github.com/beartype/beartype for runtime type enforcement; it's only at function calls, though, but probably a decent solution for codebases that are not completely typed for MyPy or pyright.

It is though, if you add a type checker to your pipeline and use it without any escape hatches such as `Any` or `type: ignore`, you are essentially making the promise that your code is statically typed. But I say it is a matter of perspective because in my opinion runtime type checking should be avoided if we can get away with statically typed code, but there are type checkers that perform runtime type checking via annotations such as [Beartype](https://github.com/beartype/beartype) (with some trickery like assuming homogenous data structures as to not have to check every element of every structure). Anyway the definition of "type safe" is not 100% even in compiled languages.

There is the beartype project.

Personally I find working around mypy's quirks to be more effort than it's worth, so to offer another option: typeguard or beartype can be used to perform run-time type checking.

I love his projects too. He's also the creator of uLisp.

http://www.ulisp.com/

Not CL, but there is ulisp (http://www.ulisp.com/) for microcontrollers, supposed to be really tiny, and there is Carp (https://github.com/carp-lang/Carp) which is without a GC so seems suitable for real-time stuff.

There's also ulisp (for Arduino projects etc.): http://www.ulisp.com/

This is larger, because there are functions for accessing peripherals, and the core is more standard lispy with 'caadr' et.al., and it has a compacting GC, so images can be saved as a compact blob.

You might consider uLisp, it's very Common Lispy for the memory constraints given (sans macros and splicing quote). And you can still connect to it and save an image. I've tried it and it works well enough. Here is the homepage.

Agreed - the interactivity is good. Lisp is close (have you seen http://www.ulisp.com/ - I can't believe they got into into that small a target!). Python is ok, but for some reason I don't use the REPL in the same way I do in Forth - I think calling functions is just harder somehow. Mostly is exploring valves from the Python REPL.