Guy Bedford

Note that the latest worker-build now uses the new experimental reinitialization support implemented in wasm bindgen. We are also working on unwind support with this now building as of the...

@nickbabcock I had no intention of stepping on your work here, but ended up working on a refactoring to the export system that had a deterministic effect in https://github.com/wasm-bindgen/wasm-bindgen/pull/4813. It...

https://github.com/wasm-bindgen/wasm-bindgen/pull/4813 has now landed which implements some of the changes here but not all of them. Hopefully this should still rebase relatively cleanly to that though since they're in different...

@nickbabcock it could certainly be worthwhile to implement parts of this into Walrus, for example providing a sort function for Walrus or sort option, but I don't think we should...

The recent `reexport` feature on imports coming in 106 next release allows "re-exporting" snippet definitions, and the new `js_namespace` and `this` feature on exports allows defining arbitrary objects and also...

Thanks for the review, this can work for us - I've updated this to use a configuration instead.

@daxpedda it requires us to write wrappers around all types, and then add send and sync to all those types. See e.g. https://github.com/search?q=repo%3Acloudflare%2Fworkers-rs%20unsafe%20impl%20Sync&type=code. So this small diff here, avoids every...

> You could instead use struct SendSyncWrapper(T);. A single wrapper that would work for all of them. What I'm hearing here is alternatives, what I don't hear is counter arguments.

> The problem with this feature is that it encourages libraries to rely on it for convenience. Which suddenly makes them incompatible with the atomic target feature even when they...

A large portion of Cloudflare Workers users use Axum, which assumes threading support for router futures, with Send and Sync as requirements. JsValue is very common in wasm bindgen apps,...