1. 14
  1. 4

    No very explicit statement of why one would want this, but it seems like the implication is you want to embed Python in your swift and you don’t want to embed cpython. Given the limitations and lack of benchmarks it seems like it’s squarely aimed at the extension language usecase.


    1. 4

      Or maybe the justification is “RWIIS all the things!” which I have no doubt exists by corollary with RWIIR.

      Or it’s just not finished yet. Note the lack of GC, or of any way to free memory without destroying the Python context … that’s kind of a big caveat for most real world use.

      Interpreters and runtimes are cool. It looks like they have some interesting code in there, like their BigNum implementation and a DSL for generating ASTs.