mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/js/rust
История
Jeff Walden 2fe4e38ce2 Bug 1659885 - Define |JS::shadow::Realm| in public shadow API in its own minimal header. r=jonco 
Differential Revision: https://phabricator.services.mozilla.com/D87536
 		2020-08-20 19:23:08 +00:00
..
etc Bug 1659885 - Define |JS::shadow::Realm| in public shadow API in its own minimal header. r=jonco 2020-08-20 19:23:08 +00:00
src Bug 1659885 - Define |JS::shadow::Object| in public shadow API in its own minimal header. r=jonco 2020-08-20 19:21:53 +00:00
tests Bug 1617369 - Reformat js/ using rustfmt r=arai,bbouvier 2020-02-27 10:29:46 +00:00
.gitignore
…
CMakeLists.txt Bug 1613176 - Enable -Wreturn-type-c-linkage. r=froydnj 2020-02-05 11:21:04 +00:00
Cargo.toml Bug 1621044 - Tentative fix for the SM-rust build bustage. 2020-03-11 00:06:44 +00:00
README.md Bug 1448324 - Fix link in js/rust readme. r=jdm 2019-10-18 14:30:52 +00:00
build.rs Bug 1659885 - Define |JS::shadow::Object| in public shadow API in its own minimal header. r=jonco 2020-08-20 19:21:53 +00:00

README.md

The js Crate: Rust Bindings to SpiderMonkey

User Documentation

Building

To build a release version of SpiderMonkey and the Rust code with optimizations enabled:

$ cargo build --release

To build with SpiderMonkey's DEBUG checks and assertions:

$ cargo build --features debugmozjs

Raw FFI bindings to JSAPI are machine generated with rust-lang-nursery/rust-bindgen, and requires libclang >= 3.9. See ./build.rs for details.

Cargo Features

  • debugmozjs: Create a DEBUG build of SpiderMonkey with many extra assertions enabled. This is decoupled from whether the crate and its Rust code is built in debug or release mode.

  • promises: Enable SpiderMonkey native promises.

  • nonzero: Leverage the unstable NonZero type. Requires nightly Rust.

Testing

Make sure to test both with and without the debugmozjs feature because various structures have different sizes and get passed through functions differently at the ABI level! At minimum, you should test with debugmozjs to get extra assertions and checking.

$ cargo test
$ cargo test --features debugmozjs