wasm-bindgen/crates/js-sys
Alex Crichton eee71de0ce
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 15:52:24 -05:00
..
src Support asynchronous tests (#600) 2018-08-01 15:52:24 -05:00
tests Support asynchronous tests (#600) 2018-08-01 15:52:24 -05:00
Cargo.toml js-sys: Add some more Cargo.toml metadata like license 2018-07-26 15:06:24 -07:00
CHANGELOG.md js-sys: Add a js-sys specific CHANGELOG.md 2018-07-26 15:05:00 -07:00
README.md Move the js module to a js_sys crate (#512) 2018-07-19 14:30:58 -05:00

js-sys

Raw bindings to JS global APIs for projects using wasm-bindgen. This crate is handwritten and intended to work in all JS environments like browsers and Node.js.

Progress for this crate can be tracked at #275.