ulisp
beartype
Our great sponsors
ulisp | beartype | |
---|---|---|
33 | 18 | |
361 | 2,350 | |
- | 5.1% | |
2.6 | 9.4 | |
12 months ago | 7 days ago | |
C++ | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ulisp
- How to Write a (Lisp) Interpreter (In Python)
- Show HN: I Made a Lisp
-
Lisp Badge LE
I love his projects too. He's also the creator of uLisp.
-
Lisp in Space
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.
-
fe: A tiny, embeddable language implemented in ANSI C
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.
- ¿Any interpreted lenguage working in low memory microcontrollers?
-
What do you think of Forth?
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.
For 'hobbists' there are lots of amazing Forths, some examples: Zeptoforth has proper threading primitives, optional FAT SD card support and is MIT licensed (important for semi-commercial binary builds), Mecrisp Forth has a native register-colouring compiler is 20K and supports ARM, RISCV, FPGA and others, Flashforth support AVR and PIC. If you like ESP32, then ESP32Forth (an eForth variant) has a ton of features worth looking at. The interactivity is amazing. Of course on PCs or embedded Linux we can do this with shells and scripting languages with REPL - but with deeply embedded microcontroller the only other thing I've seen that's close is http://www.ulisp.com/ - and although it's amazing to get Lisp this small and the developer has done cool things, mostly it's still a toy project that relies on recompiling and adding to C to do any real work. No where near the maturity of the above Forth systems.
-
Microcontroller-based Lisp machine (minimum language needed)?
Have you looked at uLisp? Or perhaps Mezzano? The latter doesn't run on bare metal yet, but does have arm64 support.
There's also ulisp to take a look at. Might suit some of your needs.
beartype
-
Writing Python Like Rust
https://github.com/beartype/beartype
I wish more people started using Beartype, it makes Python bearable
- When the client's management is happy but their dev team is a pain
-
Returning to snake's nest after a long journey, any major advances in python for science ?
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.)
-
What are some features you wish Python had?
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.
-
svg.py: Type-safe and powerful Python library to generate SVG files
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.
- Python’s “Type Hints” are a bit of a disappointment to me
-
What's the best practice to validate parameter types at runtime in Python, with and without a third-party module?
There is the beartype project.
-
Statically typed Python
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.
-
The Toit language is now open source
> dynamically checks that the type is correct
How thorough is this? Beartype is also on the front page now, and its README contains an example of dynamic type checking that takes over an hour to run [0]. How does Toit avoid being that slow?
[0] https://github.com/beartype/beartype#why-should-i-use-bearty...
- GitHub - beartype/beartype: Unbearably fast O(1) runtime type-checking in pure Python.
What are some alternatives?
typeguard - Run-time type checker for Python
pydantic - Data validation using Python type hints
mypy - Optional static typing for Python
mypyc - Compile type annotated Python to fast C extensions
ecl
Lua-RTOS-ESP32 - Lua RTOS for ESP32
ferret - Ferret is a free software lisp implementation for real time embedded control systems.
lispBM - An interpreter for a concurrent lisp-like language with message-passing and pattern-matching implemented in C.
tinyscheme - TinyScheme is easy to learn and modify. It is structured like a meta-interpreter, only it is written in C.
toit - Program your microcontrollers in a fast and robust high-level language.
benchmarks - Some benchmarks of different languages
nesper - Program the ESP32 with Nim! Wrappers around ESP-IDF API's.