Philipp Tessenow

Alright, merged the MR 🚢

Since we're preparing the aforementioned wasmtime switch (having a different memory API), I believe this ticket can be closed. Nathan, please feel free to reopen if you feel this is...

Hey @munjalpatel thanks for your question, it's a good one! :) Wasmex does currently not support dynamic linking between WASM modules. But if you're up to implement that support, I'd...

Very interesting thought @josevalim ! I like your idea of explicitly passing the answer-to pid down instead of just assuming `self()` to allow any Erlang process to receive the answer...

Awesome! I like the proposed `call_exported_function` API. --------- > I think we are blocking the client, but not the server. Ha! [[insert homer simpson d'oh! sound here]](https://en.wikipedia.org/wiki/D%27oh%21). Thanks, and I...

> I did this 100x already. So it will be quick to draft something! 💜 > One of the things that would be nice is to make WASM preemptive, which...

1. As you outlined, this approach is not scalable to many calls/threads. Async rust (depending on the async runtime) solved that with thread pools. > Also, what happens if the...

Alright, I gave approaches 2. and 3. some thinking and both are doable with different tradeoffs. I'm very interested in your experience @josevalim on what is better - do you...

@RoyalIcing this looks great! thanks for taking care! ❤️ there is just that weird dialyzer error. and just staring at the error output I sometimes wonder if it's worth having...

whoar, I guess I'll throw out dialyzer. the benefit it brings doesn't feel big enough compared to the burden of maintenance it introduces.