wasm-bindgen/tests/all/js_globals/WeakMap.rs

184 lines
4.5 KiB
Rust
Raw Normal View History

2018-06-26 11:12:32 +03:00
#![allow(non_snake_case)]
use project;
#[test]
fn new() {
project()
2018-06-28 08:42:34 +03:00
.file(
"src/lib.rs",
r#"
2018-06-26 11:12:32 +03:00
#![feature(proc_macro, wasm_custom_section)]
extern crate wasm_bindgen;
use wasm_bindgen::prelude::*;
use wasm_bindgen::js;
#[wasm_bindgen]
pub fn new_weak_map() -> js::WeakMap {
js::WeakMap::new()
}
2018-06-28 08:42:34 +03:00
"#,
)
.file(
Speed up Travis by running Webpack in fewer tests (#381) * Reorganize Travis configuration * Add a `JOB` env var descriptor to all matrix entries. Not used anywhere but is useful when viewing the whole build on Travis's web interface. * Reorganize where builds are located, moving slow builds first and fast ones last. * Change checking the CLI builds from `cargo build` to `cargo check` * Use YAML references to reduce some duplication * Print some more timing statistics for each test * Extract `Project` helper in tests to a module This'll help make it a bit more extensible over time. At the same time the methods are also slightly reorganized to read more clearly from top to bottom. * Migrate all tests away from Webpack Wepback can take a significant amount of time to execute and when it's multiplied by hundreds of tests that adds up really quickly! After investigating Node's `--experimental-modules` option it looks like it's suitable for our use so this switches all tests to using JS files (moving away from TypeScript as well) with `--experimental-modules` with Node. Tests will be selectively re-enabled with webpack and node.js specific output (that doesn't require `--experimental-modules`), coming in later commits. * Restore the node test for node.js output Ensures it's workable as-is * Only generate typescript with webpack * Only read wasm files for webpack * Skip package.json/node_modules for now * Only generate webpack config if needed * Start a dedicated test module for typescript Will hopefully verify the generated Typescript compiles OK. * Remove unneeded `node` method * Fixup some rebase conflicts * Don't run asmjs example on travis * Fixup generator tests * Attempt to fix windows * Comment windows fix * More test fixes * More exclusions * More test fixes * Relax eslint regex Catch mjs modules as well * Fix eslint * Speed up travis on examples slightly
2018-07-05 06:37:09 +03:00
"test.js",
2018-06-28 08:42:34 +03:00
r#"
2018-06-26 11:12:32 +03:00
import * as assert from "assert";
import * as wasm from "./out";
export function test() {
assert.equal(typeof wasm.new_weak_map(), "object");
}
2018-06-28 08:42:34 +03:00
"#,
)
2018-06-26 11:12:32 +03:00
.test()
}
#[test]
fn get() {
project()
2018-06-28 08:42:34 +03:00
.file(
"src/lib.rs",
r#"
2018-06-26 11:12:32 +03:00
#![feature(proc_macro, wasm_custom_section)]
extern crate wasm_bindgen;
use wasm_bindgen::prelude::*;
use wasm_bindgen::js;
#[wasm_bindgen]
pub fn get_value(this: &js::WeakMap, key: js::Object) -> JsValue {
2018-06-26 11:12:32 +03:00
this.get(key)
}
2018-06-28 08:42:34 +03:00
"#,
)
.file(
Speed up Travis by running Webpack in fewer tests (#381) * Reorganize Travis configuration * Add a `JOB` env var descriptor to all matrix entries. Not used anywhere but is useful when viewing the whole build on Travis's web interface. * Reorganize where builds are located, moving slow builds first and fast ones last. * Change checking the CLI builds from `cargo build` to `cargo check` * Use YAML references to reduce some duplication * Print some more timing statistics for each test * Extract `Project` helper in tests to a module This'll help make it a bit more extensible over time. At the same time the methods are also slightly reorganized to read more clearly from top to bottom. * Migrate all tests away from Webpack Wepback can take a significant amount of time to execute and when it's multiplied by hundreds of tests that adds up really quickly! After investigating Node's `--experimental-modules` option it looks like it's suitable for our use so this switches all tests to using JS files (moving away from TypeScript as well) with `--experimental-modules` with Node. Tests will be selectively re-enabled with webpack and node.js specific output (that doesn't require `--experimental-modules`), coming in later commits. * Restore the node test for node.js output Ensures it's workable as-is * Only generate typescript with webpack * Only read wasm files for webpack * Skip package.json/node_modules for now * Only generate webpack config if needed * Start a dedicated test module for typescript Will hopefully verify the generated Typescript compiles OK. * Remove unneeded `node` method * Fixup some rebase conflicts * Don't run asmjs example on travis * Fixup generator tests * Attempt to fix windows * Comment windows fix * More test fixes * More exclusions * More test fixes * Relax eslint regex Catch mjs modules as well * Fix eslint * Speed up travis on examples slightly
2018-07-05 06:37:09 +03:00
"test.js",
2018-06-28 08:42:34 +03:00
r#"
2018-06-26 11:12:32 +03:00
import * as assert from "assert";
import * as wasm from "./out";
export function test() {
let map = new WeakMap();
let key = {some: "key"};
map.set(key, "value");
assert.equal(wasm.get_value(map, key), "value");
let undef = "unexisting_key";
assert.equal(typeof wasm.get_value(map, undef), "undefined");
}
2018-06-28 08:42:34 +03:00
"#,
)
2018-06-26 11:12:32 +03:00
.test()
}
#[test]
fn set() {
project()
2018-06-28 08:42:34 +03:00
.file(
"src/lib.rs",
r#"
2018-06-26 11:12:32 +03:00
#![feature(proc_macro, wasm_custom_section)]
extern crate wasm_bindgen;
use wasm_bindgen::prelude::*;
use wasm_bindgen::js;
#[wasm_bindgen]
2018-06-26 22:20:36 +03:00
pub fn set_value(this: &js::WeakMap, key: js::Object, value: JsValue) -> js::WeakMap {
2018-06-26 11:12:32 +03:00
this.set(key, value)
}
2018-06-28 08:42:34 +03:00
"#,
)
.file(
Speed up Travis by running Webpack in fewer tests (#381) * Reorganize Travis configuration * Add a `JOB` env var descriptor to all matrix entries. Not used anywhere but is useful when viewing the whole build on Travis's web interface. * Reorganize where builds are located, moving slow builds first and fast ones last. * Change checking the CLI builds from `cargo build` to `cargo check` * Use YAML references to reduce some duplication * Print some more timing statistics for each test * Extract `Project` helper in tests to a module This'll help make it a bit more extensible over time. At the same time the methods are also slightly reorganized to read more clearly from top to bottom. * Migrate all tests away from Webpack Wepback can take a significant amount of time to execute and when it's multiplied by hundreds of tests that adds up really quickly! After investigating Node's `--experimental-modules` option it looks like it's suitable for our use so this switches all tests to using JS files (moving away from TypeScript as well) with `--experimental-modules` with Node. Tests will be selectively re-enabled with webpack and node.js specific output (that doesn't require `--experimental-modules`), coming in later commits. * Restore the node test for node.js output Ensures it's workable as-is * Only generate typescript with webpack * Only read wasm files for webpack * Skip package.json/node_modules for now * Only generate webpack config if needed * Start a dedicated test module for typescript Will hopefully verify the generated Typescript compiles OK. * Remove unneeded `node` method * Fixup some rebase conflicts * Don't run asmjs example on travis * Fixup generator tests * Attempt to fix windows * Comment windows fix * More test fixes * More exclusions * More test fixes * Relax eslint regex Catch mjs modules as well * Fix eslint * Speed up travis on examples slightly
2018-07-05 06:37:09 +03:00
"test.js",
2018-06-28 08:42:34 +03:00
r#"
2018-06-26 11:12:32 +03:00
import * as assert from "assert";
import * as wasm from "./out";
export function test() {
let map = new WeakMap();
let key = {some: "key"};
wasm.set_value(map, key, "value");
assert.equal(map.get(key), "value");
}
2018-06-28 08:42:34 +03:00
"#,
)
2018-06-26 11:12:32 +03:00
.test()
}
#[test]
fn has() {
project()
2018-06-28 08:42:34 +03:00
.file(
"src/lib.rs",
r#"
2018-06-26 11:12:32 +03:00
#![feature(proc_macro, wasm_custom_section)]
extern crate wasm_bindgen;
use wasm_bindgen::prelude::*;
use wasm_bindgen::js;
#[wasm_bindgen]
pub fn has_value(this: &js::WeakMap, key: js::Object) -> bool {
2018-06-26 11:12:32 +03:00
this.has(key)
}
2018-06-28 08:42:34 +03:00
"#,
)
.file(
Speed up Travis by running Webpack in fewer tests (#381) * Reorganize Travis configuration * Add a `JOB` env var descriptor to all matrix entries. Not used anywhere but is useful when viewing the whole build on Travis's web interface. * Reorganize where builds are located, moving slow builds first and fast ones last. * Change checking the CLI builds from `cargo build` to `cargo check` * Use YAML references to reduce some duplication * Print some more timing statistics for each test * Extract `Project` helper in tests to a module This'll help make it a bit more extensible over time. At the same time the methods are also slightly reorganized to read more clearly from top to bottom. * Migrate all tests away from Webpack Wepback can take a significant amount of time to execute and when it's multiplied by hundreds of tests that adds up really quickly! After investigating Node's `--experimental-modules` option it looks like it's suitable for our use so this switches all tests to using JS files (moving away from TypeScript as well) with `--experimental-modules` with Node. Tests will be selectively re-enabled with webpack and node.js specific output (that doesn't require `--experimental-modules`), coming in later commits. * Restore the node test for node.js output Ensures it's workable as-is * Only generate typescript with webpack * Only read wasm files for webpack * Skip package.json/node_modules for now * Only generate webpack config if needed * Start a dedicated test module for typescript Will hopefully verify the generated Typescript compiles OK. * Remove unneeded `node` method * Fixup some rebase conflicts * Don't run asmjs example on travis * Fixup generator tests * Attempt to fix windows * Comment windows fix * More test fixes * More exclusions * More test fixes * Relax eslint regex Catch mjs modules as well * Fix eslint * Speed up travis on examples slightly
2018-07-05 06:37:09 +03:00
"test.js",
2018-06-28 08:42:34 +03:00
r#"
2018-06-26 11:12:32 +03:00
import * as assert from "assert";
import * as wasm from "./out";
export function test() {
let map = new WeakMap();
let key = {some: "key"};
map.set(key, "value");
assert.equal(wasm.has_value(map, key), true);
let undef = "unexisting_key";
assert.equal(wasm.has_value(map, undef), false);
}
2018-06-28 08:42:34 +03:00
"#,
)
2018-06-26 11:12:32 +03:00
.test()
}
#[test]
fn delete() {
project()
2018-06-28 08:42:34 +03:00
.file(
"src/lib.rs",
r#"
2018-06-26 11:12:32 +03:00
#![feature(proc_macro, wasm_custom_section)]
extern crate wasm_bindgen;
use wasm_bindgen::prelude::*;
use wasm_bindgen::js;
#[wasm_bindgen]
pub fn delete_key(this: &js::WeakMap, key: js::Object) -> bool {
2018-06-26 11:12:32 +03:00
this.delete(key)
}
2018-06-28 08:42:34 +03:00
"#,
)
.file(
Speed up Travis by running Webpack in fewer tests (#381) * Reorganize Travis configuration * Add a `JOB` env var descriptor to all matrix entries. Not used anywhere but is useful when viewing the whole build on Travis's web interface. * Reorganize where builds are located, moving slow builds first and fast ones last. * Change checking the CLI builds from `cargo build` to `cargo check` * Use YAML references to reduce some duplication * Print some more timing statistics for each test * Extract `Project` helper in tests to a module This'll help make it a bit more extensible over time. At the same time the methods are also slightly reorganized to read more clearly from top to bottom. * Migrate all tests away from Webpack Wepback can take a significant amount of time to execute and when it's multiplied by hundreds of tests that adds up really quickly! After investigating Node's `--experimental-modules` option it looks like it's suitable for our use so this switches all tests to using JS files (moving away from TypeScript as well) with `--experimental-modules` with Node. Tests will be selectively re-enabled with webpack and node.js specific output (that doesn't require `--experimental-modules`), coming in later commits. * Restore the node test for node.js output Ensures it's workable as-is * Only generate typescript with webpack * Only read wasm files for webpack * Skip package.json/node_modules for now * Only generate webpack config if needed * Start a dedicated test module for typescript Will hopefully verify the generated Typescript compiles OK. * Remove unneeded `node` method * Fixup some rebase conflicts * Don't run asmjs example on travis * Fixup generator tests * Attempt to fix windows * Comment windows fix * More test fixes * More exclusions * More test fixes * Relax eslint regex Catch mjs modules as well * Fix eslint * Speed up travis on examples slightly
2018-07-05 06:37:09 +03:00
"test.js",
2018-06-28 08:42:34 +03:00
r#"
2018-06-26 11:12:32 +03:00
import * as assert from "assert";
import * as wasm from "./out";
export function test() {
let map = new WeakMap();
let key = {some: "key"};
map.set(key, "value");
assert.equal(wasm.delete_key(map, key), true);
assert.equal(map.has(key), false);
assert.equal(wasm.delete_key(map, key), false);
}
2018-06-28 08:42:34 +03:00
"#,
)
2018-06-26 11:12:32 +03:00
.test()
2018-06-28 08:42:34 +03:00
}