Live data from Hacker News

SPy: An interpreter and compiler for a fast statically typed variant of Python

antocuni.eu

131–133 of 133 posts

Re: SPy: An interpreter and compiler for a fast statically typed variant of Python

#131

As a prospective user the first thing I look for is lists, list comprehension, list slices, string methods, zip, zip*, tuple destructuring, generators, dicts and sets. These data structures, their syntax, and associated methods are what make Python a joy to use. They are what make it possible to solve a puzzle in a one-liner. The examples in the playground are neat but I don’t see any of the Python bread and butter u…

yes (work in progress :))

Great, thank you, I will watch with interest. The killer feature seems to be interoperability with existing CPython libraries. Best of luck!

Re: SPy: An interpreter and compiler for a fast statically typed variant of Python

#132
post #119
post #105

Earlier quoted context omitted.

I haven't, but not surprised given some of the very aggressive (in a good way) things they've done to address performance. It's impressive. I spoke to Chris Seaton back when it was getting started, and loved many of the things they were doing. Personally I want something leaner, and self-hosting, but that's also why mine is still experimental and wildly incomplete and TruffleRuby works for a lot of things.

Here, I don't know all the details, just remember having seen some talks about this in the past. It builds on top of this effort, https://medium.com/graalvm/graalvm-llvm-toolchain-f606f995bf "From Interpreting C Extensions to Compiling Them" https://eregon.me/blog/assets/research/from-interpreting-c-e...

Thanks, will definitely give it a read.

Re: SPy: An interpreter and compiler for a fast statically typed variant of Python

#133

Earlier quoted context omitted.

I have asked about using RPython as a generic standalone language before. I think the official statement is that is was never intended to become one, and it's really a very minimal subset of Python (so basically no existing Python code will run, it would require heavy refactoring or complete rewrite), and it's only specifically those features that they currently need, and it might also be a moving target, and they do…

A general purpose language should be suitable to writing its own compiler. If it's to slow for that, what's the point?

A general purpose compiled language should be suitable for writing its own compiler, but I don’t think the same holds true for interpreted languages.
Post reply on HN