2 ms·
Well judging from the description, "native" actually means writing it in RPython (a "restricted" Python with types for use in the PyPy Project for static analys
by 616c 12y ago
Well judging from the description, "native" actually means writing it in RPython (a "restricted" Python with types for use in the PyPy Project for static analysis and speeding things up[0]) and then compiling it down using PyPy (I am guessing on the second part). That could be neat, the HyLang people (Lisp written in vanilla CPython Python; I think no C extensions AFAIK).
[0] http://pypy.readthedocs.org/en/latest/coding-guide.html#id1 http://pypy.readthedocs.org/en/latest/coding-guide.html#id1
- dTal 12y agoHy isn't a full Lisp interpreter in Python, it's an s-expression to Python AST parser, which means it does everything Python does (including C extensions) at essentially native speed anyway - you can even write RPython in it. If you ask me, full Python interop makes Hy the most practical s-expression language today.
- JasonFruit 12y agoOne problem with Hy for me is that it keeps Python scoping, either global or function; that doesn't feel natural to me in a Lisp, and it gets in my way. If it weren't for that and a few similar matters, I'd agree with you on Hy's practicality; as it is, I'd give my nod to Clojure.