Skip to content

Remove wasm bindgen futures#1001

Open
guybedford wants to merge 2 commits into
mainfrom
remove-wasm-bindgen-futures
Open

Remove wasm bindgen futures#1001
guybedford wants to merge 2 commits into
mainfrom
remove-wasm-bindgen-futures

Conversation

@guybedford

Copy link
Copy Markdown
Collaborator

This removes the use of the wasm-bindgen-futures crate, with the last commit based to #999 and using PR wasm-bindgen/wasm-bindgen#5164.

worker-build sets WASM_BINDGEN_USE_JS_SYS=1, so the #[wasm_bindgen] macro
emits js_sys::futures glue directly and the worker crate no longer needs
wasm-bindgen-futures. Drop the dependency and the re-export, and migrate
the remaining direct users to js_sys::futures.
@guybedford guybedford force-pushed the remove-wasm-bindgen-futures branch from 165d961 to c4cbcdb Compare June 9, 2026 00:56
@codspeed-hq

codspeed-hq Bot commented Jun 9, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

✅ 2 untouched benchmarks


Comparing remove-wasm-bindgen-futures (fe9d953) with main (ea4177d)

Open in CodSpeed

worker-build only sets the env var for the wasm build, but plain
`cargo check`/`cargo clippy` also expand #[wasm_bindgen] on async fns
(e.g. email.rs) and the generated glue references wasm_bindgen_futures.
Set the opt-in in .cargo/config.toml [env] so the proc-macro emits
js_sys::futures glue for host builds too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant