d6b56823da
The CacheIR code only sees transparent CCWs so it's fine to do a static unwrap. DebuggerObject::unwrap is more complicated. We're in the debugger's compartment there; I went with UnwrapOneCheckedStatic as it seems safest and simplest for now. Differential Revision: https://phabricator.services.mozilla.com/D21354 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| etc | ||
| src | ||
| tests | ||
| .gitignore | ||
| CMakeLists.txt | ||
| Cargo.toml | ||
| README.md | ||
| build.rs | ||
README.md
The js Crate: Rust Bindings to SpiderMonkey
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 unstableNonZerotype. 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