tlsnotary/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/tlsnotary/wasm-bindgen.git synced 2026-01-09 21:58:02 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update passing-rust-closures-to-js.md (#3859)

Browse Source
This commit is contained in:
Doug A
2024-02-28 10:59:05 -04:00
committed by GitHub
parent b9ccb8f3c5
commit 002307746e
1 changed files with 0 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
guide/src/reference/passing-rust-closures-to-js.md
View File

@@ -63,12 +63,6 @@ return but the JavaScript closure still needs to be valid!
For this scenario, you need the `Closure` type, which is defined in the
`wasm_bindgen` crate, exported in `wasm_bindgen::prelude`, and represents a
"long lived" closure.
The `Closure` type is currently behind a feature which needs to be enabled:
```toml
[dependencies]
wasm-bindgen = {version = "^0.2", features = ["nightly"]}
```
The validity of the JavaScript closure is tied to the lifetime of the `Closure`
in Rust. **Once a `Closure` is dropped, it will deallocate its internal memory