Tricster

Here's the stack trace. ``` 34: ==2034831==ERROR: AddressSanitizer: SEGV on unknown address 0x7f2afd9fc150 (pc 0x7f2afd0c009b bp 0x7fff25932f10 sp 0x7fff25932dd0 T0) 34: ==2034831==The signal is caused by a READ memory access....

After comment out those two lines, the seg fault goes away but there are still leaks. the log: [rust_test.log](https://github.com/metacall/core/files/9157037/rust_test.log)

I am into this.

After hacking the network part of `mio` and `tokio`, both of them works for minimal cases. There are more works to do, including: 1. implement missing functions for `mio` and...

Now we have support of the following libraries: 1. [mio](https://github.com/WasmEdge/mio/tree/wasmedge) and [tokio](https://github.com/WasmEdge/tokio/tree/wasmedge): async runtime 2. [hyper](https://github.com/WasmEdge/hyper/tree/wasmedge): An HTTP library for Rust. (client and server) 3. [reqwest](https://github.com/WasmEdge/reqwest/tree/wasmedge): An ergonomic, batteries-included HTTP...

Hi, @juntao I test tokio single-thread executor in wasi and it works. The next step would be refactoring the wasmedge_wasi_socket to asyncify it. Maybe we can just use tokio or...

Sure. Here's a minimal example. ```rust use tokio::runtime; fn main() { let basic_rt = runtime::Builder::new_current_thread().build().unwrap(); basic_rt.block_on(async { println!("Hello from async"); let fut = async { 1 + 2 }; let...

`mio` adds limited tcp support as discussed here https://github.com/tokio-rs/mio/pull/1549. So yes, the first step would be making `wasmedge_wasi_socket` work for `mio`. And `tokio` also uses `socket2`, I think we need...

Currently, I make a working single-thread wasi runtime. However, since we can not block the thread in wasm, the runtime has to poll the futures continously in a loop. It...

Yes, it would nice if a wasm program can **pause itself** when there's nothing to do, and be resumed **by the host program** when some condition is met. Let's say...