Guy Bedford

Closing as resolved, but will continue to investigate the possible memory optimization here in https://github.com/cloudflare/workers-rs/pull/832.

For what it is worth, ComponentizeJS does the same thing here - https://github.com/bytecodealliance/ComponentizeJS/blob/main/crates/spidermonkey-embedding-splicer/src/splice.rs#L679, by synthesizing the post-return functions as necessary to wrap the global bump deallocator. I don't find the...

Try building with these options, leaving out `debug` so you can get proper error messages: ``` disableFeatures: ['random', 'http', 'clocks'] ``` The resource import as you have written looks correct...

~~Note that `TextEncoder.prototype.encodeInto` is also pending implementation.~~

CI seems to be failing here after rebase. Agreed this is the better user experience, would be happy to land it for the next major release after the current patch...

I posted https://github.com/cloudflare/workers-rs/pull/861 here which just removes send entirely. Putting this one out there as a stake to question why we need this at all. At the very least I...

Ok, so just to get my head clear on the framing - `SendFuture` and `SendWrapper` are effectively wasm-bindgen helpers to allow single threaded apps to treat JS types as send....

What if we just had a wasm bindgen flag like `wasm-bindgen --unsafe-single-threaded-send` that made all JS types unsafe send?

wasm-bindgen supports threading fine - so we would not allow the flag to exist alongside any use of threading. Let me see if I can hack something together, will post...

Yeah it all seems to work, implemented https://github.com/wasm-bindgen/wasm-bindgen/pull/4770 and applied this to https://github.com/cloudflare/workers-rs/pull/861. Further feedback welcome.