wasm-bindgen/tests/wasm/main.rs

#![cfg(target_arch = "wasm32")]

extern crate js_sys;
extern crate wasm_bindgen;
extern crate wasm_bindgen_test;
extern crate wasm_bindgen_test_crate_a;
extern crate wasm_bindgen_test_crate_b;

#[cfg(feature = "serde-serialize")]
#[macro_use]
extern crate serde_derive;

use wasm_bindgen::prelude::*;

pub mod api;
pub mod arg_names;
pub mod char;
pub mod classes;
pub mod closures;
pub mod comments;
pub mod duplicate_deps;
pub mod duplicates;
pub mod enums;
#[path = "final.rs"]
pub mod final_;
pub mod getters_and_setters;
pub mod import_class;
pub mod imports;
pub mod js_objects;
pub mod jscast;
pub mod math;
pub mod no_shims;
pub mod node;
pub mod option;
pub mod optional_primitives;
pub mod rethrow;
pub mod simple;
pub mod slice;
pub mod structural;
pub mod u64;
pub mod validate_prt;
pub mod variadic;
pub mod vendor_prefix;

// should not be executed
#[wasm_bindgen(start)]
pub fn start() {
    panic!();
}
Start migrating `wasm_bindgen` tests to `wasm_bindgen_test` (#602) This commit starts migrating the `wasm_bindgen` tests to the `wasm_bindgen_test` framework, starting to assemble the coffin for `wasm-bindgen-test-project-builder`. Over time all of the tests in `tests/all/*.rs` should be migrated to `wasm_bindgen_test`, although they may not all want to go into a monolithic test suite so we can continue to test for some more subtle situations with `#[wasm_bindgen]`. In the meantime those, the `tests/all/api.rs` tests can certainly migrate! 2018-08-01 14:19:19 -05:00			`#![cfg(target_arch = "wasm32")]`

Add an accessor for wasm's own memory as a JS object In addition to closing #495 this'll be useful eventually when instantiating multiple wasm modules from Rust as you'd now be able to acquire a reference to the current module in Rust itself. 2018-08-21 10:42:52 -07:00			`extern crate js_sys;`
Start migrating `wasm_bindgen` tests to `wasm_bindgen_test` (#602) This commit starts migrating the `wasm_bindgen` tests to the `wasm_bindgen_test` framework, starting to assemble the coffin for `wasm-bindgen-test-project-builder`. Over time all of the tests in `tests/all/*.rs` should be migrated to `wasm_bindgen_test`, although they may not all want to go into a monolithic test suite so we can continue to test for some more subtle situations with `#[wasm_bindgen]`. In the meantime those, the `tests/all/api.rs` tests can certainly migrate! 2018-08-01 14:19:19 -05:00			`extern crate wasm_bindgen;`
cargo +nightly fmt --all Rustfmt all the things! 2018-09-26 08:26:00 -07:00			`extern crate wasm_bindgen_test;`
Migrate rest of `dependencies` test to `wasm` 2018-08-06 10:42:08 -07:00			`extern crate wasm_bindgen_test_crate_a;`
			`extern crate wasm_bindgen_test_crate_b;`
Start migrating `wasm_bindgen` tests to `wasm_bindgen_test` (#602) This commit starts migrating the `wasm_bindgen` tests to the `wasm_bindgen_test` framework, starting to assemble the coffin for `wasm-bindgen-test-project-builder`. Over time all of the tests in `tests/all/*.rs` should be migrated to `wasm_bindgen_test`, although they may not all want to go into a monolithic test suite so we can continue to test for some more subtle situations with `#[wasm_bindgen]`. In the meantime those, the `tests/all/api.rs` tests can certainly migrate! 2018-08-01 14:19:19 -05:00
Migrate the `serde-serialize` test to `wasm` 2018-08-06 09:43:55 -07:00			`#[cfg(feature = "serde-serialize")]`
			`#[macro_use]`
			`extern crate serde_derive;`

Add a `#[wasm_bindgen(start)]` attribute This commit adds a new attribute to `#[wasm_bindgen]`: `start`. The `start` attribute can be used to indicate that a function should be executed when the module is loaded, configuring the `start` function of the wasm executable. While this doesn't necessarily literally configure the `start` section, it does its best! Only one crate in a crate graph may indicate `#[wasm_bindgen(start)]`, so it's not recommended to be used in libraries but only end-user applications. Currently this still must be used with the `crate-type = ["cdylib"]` annotation in `Cargo.toml`. The implementation here is somewhat tricky because of the circular dependency between our generated JS and the wasm file that we emit. This circular dependency makes running initialization routines (like the `start` shim) particularly fraught with complications because one may need to run before the other but bundlers may not necessarily respect it. Workarounds have been implemented for various emission strategies, for example calling the start function directly after exports are wired up with `--no-modules` and otherwise working around what appears to be a Webpack bug with initializers running in a different order than we'd like. In any case, this in theory doesn't show up to the end user! Closes #74 2018-11-28 09:25:51 -08:00			`use wasm_bindgen::prelude::*;`

Start migrating `wasm_bindgen` tests to `wasm_bindgen_test` (#602) This commit starts migrating the `wasm_bindgen` tests to the `wasm_bindgen_test` framework, starting to assemble the coffin for `wasm-bindgen-test-project-builder`. Over time all of the tests in `tests/all/*.rs` should be migrated to `wasm_bindgen_test`, although they may not all want to go into a monolithic test suite so we can continue to test for some more subtle situations with `#[wasm_bindgen]`. In the meantime those, the `tests/all/api.rs` tests can certainly migrate! 2018-08-01 14:19:19 -05:00			`pub mod api;`
Preserve argument names 2019-03-14 08:46:42 -03:00			`pub mod arg_names;`
Migrate wasm-bindgen `char` test to `wasm` 2018-08-04 11:25:29 -07:00			`pub mod char;`
Migrate wasm-bindgen `classes` test to `wasm` 2018-08-04 11:52:21 -07:00			`pub mod classes;`
Port tests that use only basic features 2018-08-05 05:00:16 +03:00			`pub mod closures;`
Move `comments` test to `wasm` 2018-08-06 11:46:23 -07:00			`pub mod comments;`
Migrate rest of `dependencies` test to `wasm` 2018-08-06 10:42:08 -07:00			`pub mod duplicate_deps;`
Port tests that use only basic features 2018-08-05 05:00:16 +03:00			`pub mod duplicates;`
			`pub mod enums;`
Rename `host_binding` to `final` 2018-11-09 07:59:48 -08:00			`#[path = "final.rs"]`
			`pub mod final_;`
Getters/Setters for fields 2019-04-30 10:26:03 -03:00			`pub mod getters_and_setters;`
Migrate the `import_class` to `wasm` 2018-08-05 09:12:23 -07:00			`pub mod import_class;`
Migrate rest of `dependencies` test to `wasm` 2018-08-06 10:42:08 -07:00			`pub mod imports;`
Port tests that use only basic features 2018-08-05 05:00:16 +03:00			`pub mod js_objects;`
Implement `JsCast` for all imported types This commit implements the `JsCast` trait automatically for all imported types in `#[wasm_bindgen] extern { ... }` blocks. The main change here was to generate an `instanceof` shim for all imported types in case it's needed. All imported types now also implement `AsRef<JsValue>` and `AsMut<JsValue>` 2018-08-04 09:41:59 -07:00			`pub mod jscast;`
Port tests that use only basic features 2018-08-05 05:00:16 +03:00			`pub mod math;`
cli-support: Skip generating JS shims for imports when unnecessary After this change, any import that only takes and returns ABI-safe numbers (signed integers less than 64 bits and unrestricted floating point numbers) will be a direct import, and will not have a little JS shim in the middle. We don't have a great mechanism for testing the generated bindings' contents -- as opposed to its behavior -- but I manually verified that everything here does the Right Thing and doesn't have a JS shim: ```rust \#[wasm_bindgen] extern "C" { fn trivial(); fn incoming_i32() -> i32; fn incoming_f32() -> f32; fn incoming_f64() -> f64; fn outgoing_i32(x: i32); fn outgoing_f32(y: f32); fn outgoing_f64(z: f64); fn many(x: i32, y: f32, z: f64) -> i32; } ``` Furthermore, I verified that when our support for emitting native `anyref` is enabled, then we do not have a JS shim for the following import, but if it is disabled, then we do have a JS shim: ```rust \#[wasm_bindgen] extern "C" { fn works_when_anyref_support_is_enabled(v: JsValue) -> JsValue; } ``` Fixes #1636. 2019-07-10 14:22:13 -07:00			`pub mod no_shims;`
Move `node` test over to `wasm` 2018-08-06 10:06:45 -07:00			`pub mod node;`
Add tests for by-value options 2018-08-02 22:23:11 -07:00			`pub mod option;`
Rename the test 2018-08-03 20:47:03 +03:00			`pub mod optional_primitives;`
Allow returning `Result` from functions This commit adds support for exporting a function defined in Rust that returns a `Result`, translating the `Ok` variant to the actual return value and the `Err` variant to an exception that's thrown in JS. The support for return types and descriptors was rejiggered a bit to be a bit more abstract and more well suited for this purpose. We no longer distinguish between functions with a return value and those without a return value. Additionally a new trait, `ReturnWasmAbi`, is used for converting return values. This trait is an internal implementation detail, however, and shouldn't surface itself to users much (if at all). Closes #841 2018-09-17 18:26:45 -07:00			`pub mod rethrow;`
Move most of the "simple" test to the `wasm` suite 2018-08-06 09:20:19 -07:00			`pub mod simple;`
Port tests that use only basic features 2018-08-05 05:00:16 +03:00			`pub mod slice;`
			`pub mod structural;`
			`pub mod u64;`
			`pub mod validate_prt;`
[wip] support variadic javascript function parameters 2018-08-18 22:15:29 +01:00			`pub mod variadic;`
Rename `polyfill` to `vendor_prefix` cc #906 2018-10-01 12:33:33 -07:00			`pub mod vendor_prefix;`
Add a `#[wasm_bindgen(start)]` attribute This commit adds a new attribute to `#[wasm_bindgen]`: `start`. The `start` attribute can be used to indicate that a function should be executed when the module is loaded, configuring the `start` function of the wasm executable. While this doesn't necessarily literally configure the `start` section, it does its best! Only one crate in a crate graph may indicate `#[wasm_bindgen(start)]`, so it's not recommended to be used in libraries but only end-user applications. Currently this still must be used with the `crate-type = ["cdylib"]` annotation in `Cargo.toml`. The implementation here is somewhat tricky because of the circular dependency between our generated JS and the wasm file that we emit. This circular dependency makes running initialization routines (like the `start` shim) particularly fraught with complications because one may need to run before the other but bundlers may not necessarily respect it. Workarounds have been implemented for various emission strategies, for example calling the start function directly after exports are wired up with `--no-modules` and otherwise working around what appears to be a Webpack bug with initializers running in a different order than we'd like. In any case, this in theory doesn't show up to the end user! Closes #74 2018-11-28 09:25:51 -08:00
			`// should not be executed`
			`#[wasm_bindgen(start)]`
			`pub fn start() {`
			`panic!();`
			`}`