[Feature] First-class support for languages other than TypeScript. (WebAssembly Interface Types.)

[brillout]

WebAssembly Interface Types will make it more seamless to write and consume modules written in other high-level languages. AFAICT the only main restriction would then be the performance drawback of values being copied back and forth.

I'm imagining a Deno future where I will be able to write one module in Rust, another in Python (once WebAssembly GC is implemented), and one in TypeScript. But I'm left with many questions.

• Would I be able to simply deno run and Deno would run the Rust and Python compilers for me?
• Would I be able to load a Rust module from within another Rust module with URLs? Not sure how this could work since language compilers don't understand module URLs. Maybe a precompilation step that transforms URLs into filesystem paths.
• Will WASI eventually replace most Deno functions?

Thoughts? Is that a future Deno is interested in?

It would lovely to be able to seamlessly write a frontend in TypeScript with a backend in Rust, while using a machine learning library written in Python. All that using the Deno runtime.

[emadurandal]

Hi, I like this topic. Recently I like ReScript language. https://rescript-lang.org/docs/manual/latest/introduction

It doesn't support WebAssembly so far, but the ReScript's compile speed is good for this problem. I guess. https://docs.google.com/document/d/1_WvwHl7BXUPmoiSeD8G83JmS8ypsTPqed4Btkqkn_-4/preview?pru=AAABcrrKL5k*nQ4LS569NsRRAce2BVanXw#