WebAssembly Support about ractor HOT 1 OPEN

This is awesome! I don't think the implementation looks that janky actually, I understand the implementation requirements around JoinHandle but that could be cleaned up relatively easily I think (that's probably quite tokio specific tbh).

Tokio's default I/O channels (tokio::sync::mpsc, etc) are all runtime independent and I'm glad they seem to work with in WASM.

One thing though, it looks like if we enable tracing, we're back onto the tokio runtime? I feel like maybe in WASM it would make sense to just ignore the tracing configuration bit and not spawn anything named (as it's really only a feature for tokio-console to assist identifying which tasks are which actors). Also 1 small nit, I wonder if it'd be better to utilize a shared macro or something if we're going to share implementations (i.e. the select! statement in your wasm_primatives module).

Does everything work as expected? The tests all pass on a WASM runtime? You can also try out the examples and benchmarks to see how it does!

If we clean it up a bit, this would be a great PR :)

from ractor.