gecko-dev/js/rust
Sylvestre Ledru 31e4471215 Bug 1617369 - Reformat js/ using rustfmt r=arai,bbouvier
Differential Revision: https://phabricator.services.mozilla.com/D63952

--HG--
extra : moz-landing-system : lando
2020-02-27 10:29:46 +00:00
..
etc Bug 1602882 - Move array operations to a new js/Array.h header. r=sfink,bzbarsky 2019-12-11 06:17:44 +00:00
src Bug 1617369 - Reformat js/ using rustfmt r=arai,bbouvier 2020-02-27 10:29:46 +00:00
tests Bug 1617369 - Reformat js/ using rustfmt r=arai,bbouvier 2020-02-27 10:29:46 +00:00
.gitignore
build.rs Bug 1617369 - Reformat js/ using rustfmt r=arai,bbouvier 2020-02-27 10:29:46 +00:00
Cargo.toml
CMakeLists.txt Bug 1613176 - Enable -Wreturn-type-c-linkage. r=froydnj 2020-02-05 11:21:04 +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