wasm-bindgen/crates/futures/Cargo.toml

[package]
name = "wasm-bindgen-futures"
version = "0.2.16"
authors = ["The wasm-bindgen Developers"]

[dependencies]
futures = "0.1.20"
js-sys = { path = "../js-sys", version = '0.2.1' }
wasm-bindgen = { path = "../..", version = '0.2.16' }

[target.'cfg(target_arch = "wasm32")'.dev-dependencies]
wasm-bindgen-test = { path = '../test', version = '0.2.16' }
Support asynchronous tests (#600) * Tweak the implementation of heap closures This commit updates the implementation of the `Closure` type to internally store an `Rc` and be suitable for dropping a `Closure` during the execution of the closure. This is currently needed for promises but may be generally useful as well! * Support asynchronous tests This commit adds support for executing tests asynchronously. This is modeled by tests returning a `Future` instead of simply executing inline, and is signified with `#[wasm_bindgen_test(async)]`. Support for this is added through a new `wasm-bindgen-futures` crate which is a binding between the `futures` crate and JS `Promise` objects. Lots more details can be found in the details of the commit, but one of the end results is that the `web-sys` tests are now entirely contained in the same test suite and don't need `npm install` to be run to execute them! * Review tweaks * Add some bindings for `Function.call` to `js_sys` Name them `call0`, `call1`, `call2`, ... for the number of arguments being passed. * Use oneshots channels with `JsFuture` It did indeed clean up the implementation! 2018-08-01 23:52:24 +03:00			`[package]`
			`name = "wasm-bindgen-futures"`
Bump to version 0.2.16 2018-08-14 00:25:05 +03:00			`version = "0.2.16"`
Support asynchronous tests (#600) * Tweak the implementation of heap closures This commit updates the implementation of the `Closure` type to internally store an `Rc` and be suitable for dropping a `Closure` during the execution of the closure. This is currently needed for promises but may be generally useful as well! * Support asynchronous tests This commit adds support for executing tests asynchronously. This is modeled by tests returning a `Future` instead of simply executing inline, and is signified with `#[wasm_bindgen_test(async)]`. Support for this is added through a new `wasm-bindgen-futures` crate which is a binding between the `futures` crate and JS `Promise` objects. Lots more details can be found in the details of the commit, but one of the end results is that the `web-sys` tests are now entirely contained in the same test suite and don't need `npm install` to be run to execute them! * Review tweaks * Add some bindings for `Function.call` to `js_sys` Name them `call0`, `call1`, `call2`, ... for the number of arguments being passed. * Use oneshots channels with `JsFuture` It did indeed clean up the implementation! 2018-08-01 23:52:24 +03:00			`authors = ["The wasm-bindgen Developers"]`

			`[dependencies]`
			`futures = "0.1.20"`
Bump js-sys to 0.2.1 2018-08-14 00:32:52 +03:00			`js-sys = { path = "../js-sys", version = '0.2.1' }`
Bump to version 0.2.16 2018-08-14 00:25:05 +03:00			`wasm-bindgen = { path = "../..", version = '0.2.16' }`
futures: Add sanity tests for conversion between Promises and Futures Part of #614 2018-08-10 02:21:12 +03:00
			`[target.'cfg(target_arch = "wasm32")'.dev-dependencies]`
Bump to version 0.2.16 2018-08-14 00:25:05 +03:00			`wasm-bindgen-test = { path = '../test', version = '0.2.16' }`