gecko-dev/js/rust
Jeff Walden 933368cb18 Bug 1663365 - Move DOM proxy-related details (including expand support) to separate headers out of jsfriendapi.h. r=jandem
Differential Revision: https://phabricator.services.mozilla.com/D89336
2020-09-08 22:57:14 +00:00
..
etc Bug 1663365 - Move |JSJitInfo| out of jsfriendapi.h to its own experimental header. r=jandem 2020-09-08 22:52:34 +00:00
src Bug 1663365 - Move |JSJitInfo| out of jsfriendapi.h to its own experimental header. r=jandem 2020-09-08 22:52:34 +00:00
tests
.gitignore
CMakeLists.txt
Cargo.toml Bug 1621044 - Tentative fix for the SM-rust build bustage. 2020-03-11 00:06:44 +00:00
README.md
build.rs Bug 1663365 - Move DOM proxy-related details (including expand support) to separate headers out of jsfriendapi.h. r=jandem 2020-09-08 22:57:14 +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