Richard Musiol

There is now a table that shows which browsers/engines support which WebAssembly features: https://webassembly.org/roadmap/ Unfortunately Safari is still showing no effort at all to keep up with the evolution of...

> I hope that decisions is not made lightly Just collecting data and feedback at the moment. > Safari has almost a 17% market share according to these metrics Yes,...

> Do you mean "compile time" as in during go tool compile, or "link time" as in go tool link? If the latter, it may be worth making wasm-opt optional...

> Another reason Asyncify is fast is that we analyze the entire program’s call graph to see which functions might unwind, so that we can avoid modifying functions that can’t....

This is a good question. I hadn't considered it yet. Yes, it switches the Go stack, but do we also have to switch the WebAssembly stack? Couldn't we simply continue...

> Also, once we have threads, we can have preemptions. Preemption check is also at function entries, and morestack is dual-functioned. In this case, we'll do a real goroutine switch....

> If it would be useful, I could look into porting the Binaryen CFG code (which is ~2,000 lines of C++ that I wrote, and that uses an improved Relooper...

We are also now using `compilerOptions.paths` to switch to absolute import paths. We would love to see this feature implemented. For now we are using a patch: ```diff diff --git...

I now managed to solve this without resorting to a patch by using the [webpackConfig option](https://github.com/sverweij/dependency-cruiser/blob/develop/doc/options-reference.md#webpackconfig-use-the-resolution-options-of-a-webpack-configuration) with a config file that only provides the `resolve.alias` option.

I'm not a rust dev (yet), so I can not easily contribute directly. My current focus is on adding support for wasi to Go.