Hacker News Reader

I presume they don't include internal IRs like Python bytecode, as it's not any kind of shared or standardised format. Otherwise you'd be including tons of different compiler IRs.

I thought it maps your code to the base Py_Object like how writing an extension works? Idk only done a little bit of that and need to dive into the process more. On my todo list so if you have some links that have a good explanation of this that would be great. Unfortunately was unable to take compilers in school so missed out on the conceptual aspect of the compilation process.

edit: found the docs on python.org for the compiler [1]

[1] https://devguide.python.org/compiler/

Yeah it doesn’t compile it into C though.

You may be thinking of Cython, which compiles a language similar to Python, but not quite Python, into C using the Python C extension interface.

(A subset of) Clojure can be compiled to C++ using the Ferret compiler: https://ferret-lang.org/

Also OCaml to OCaml bytecode via ocamlc to Javascript via js_of_ocaml.

Also, rust to webassembly

I think the correct representation of this is Rust to LLVM IR (which is there), then LLVM to WebAssembly (which should be there but isn't).

Actually, WebAssembly as a compile target is just generally not there on the graph, which is weird. The Wasm compiler scene is pretty rapidly fluctuating though.

Reply on news.ycombinator.com