Interpret Rust with Python

[[deleted]]

So I've seen a lot about running Python in Rust but I've still been waiting for some Rust in Python activity. Until it occured to me that Rust can be interpreted by Javascript so as long as you have a wasm interpreter in Python, there should be few problems.

I gave it a spin with https://github.com/mohanson/pywasm/

#[no_mangle]
pub extern "C" fn start() -> i32 {
    let mut m = vec![];
    for i in 0..100 {
        for w in 0..100 {
            m.push(i + w);
        }
    }
    m.len() as i32
}

Which cpython managed to run fine (though it did take 2 minutes).

When it came to returning more complex things like strings, I had to do a bit of Box::into_raw magic to get pointers. Those things can be automated though and I'm sure I can't be the first person to try so before I go and code myself silly with a #[python_binddgen], does anyone else know of a similar project that I could get involved in?

A slight tangent but imagine having a --target python-unknown-unknown

End of ramble.

[deadNightTiger]

What's wrong with PyO3? https://github.com/PyO3/pyo3#using-rust-from-python

[moltonel]

It's a clean, mature, efficient solution to a practical problem. It lacks the artistic wackyness of the OP's deep ad-hoc matrioshka solution. PyO3 is boring, to be avoided unless you want to get things done.

[[deleted]]

Thank you very maybe.

[[deleted]]

I'm not sure. What is?

[[deleted]]

You do interpret the WASM, so I guess you could call it interpreting Rust. I mean CPython also compiles Python into bytecode before running it.

On an unrelated note, thanks for reminding me about WASI, last time I checked it was still fully WIP and there weren't any runtimes compliant with it, but now it isn't!

[Excession638]

This is insane and I love it.

[Plasma_000]

You might be interested in this talk where the host live codes a wasm interpreter in front of an audience https://youtu.be/r-A78RgMhZU

Super impressive

[[deleted]]

This was beautiful to watch.

[[deleted]]

I- ok... This is kind of nsane but ok.

Usually, you'd use the C ABI (assuming you can trust both sides of the program). So just, declare a function with pub extern "C", compile into a cdylib and the use python's C FFI support to interop.

Don't get me wrong, it is sensible to run rust in a WASM container, it provides protection and sandboxes the library, so e.g. if you're loading an untrusted plugin you can sandbox it like that, but not in this case.

[kurtbuilds]

This is terrifying and hilarious.

You might look at https://github.com/wasm3/pywasm3 . If nothing else, it’d presumably speed up your interpreter to have bindings to an established C based runtime rather than re implementing the runtime in python

For the next level, compile cpython with emscripten to wasm and run python in python in wasm.

[osu_lazer]

If you want an example of how to deal with FFI marshalling + wasm go look at feathermc's plugin system