Jens Reimann

Technically yes … but simply fetching a new tool because of a version mismatch might also be a bit problematic. Trunk would need to figure out that it is not...

Trunk is "just" a build tool for Rust based WebAssembly applications (for the browser). In general, I think that should work with `wasm_thread`. I might just be that the way...

I don't think that's possible … yet! It might make sense to add that using a `data-` attribute (`data-z`?). It's definitely for the "pro" user :)

So according to the cargo documentation, you can already do this with cargo alone: https://doc.rust-lang.org/cargo/reference/unstable.html > Anything which can be configured with a `-Z` flag can also be set in...

Ok, I think I know what the problem is. Trunk creates the bootstrapper for the wasm initialization. And wasm_thread requires a specific entry point to be called: ``` wasm_bindgen('./target/simple_bg.wasm').then((wasm) =>...

> That would be great. I think being able to run multi-threaded code using "native std::threads" (not just standard webworkers) would be very useful. However, the result will not be...

Ok, digging a bit more into this: It looks like it creates a new worker, and then tries to send over the "memory" of the original WASM module. Which feels...

I like this PR. But I think it would be the right time to also add some tests, to ensure this outcome is what is expected.

I think this looks good. I am just not sure when to merge it, as that would start the 0.19.x release cycle. I think there are a few other things...

@OmmyZhang I might merge a few other before merging this breaking change. Don't worry about rebasing, I will do that before/when I merge this.