Hi, folks. How does the SpiderMonkey team feel about moving the Servo
project's Rust JSAPI bindings from the separate github repo
<https://github.com/servo/rust-mozjs> they're in now into js/src in Mozilla
Central?

Two weeks ago I posted a message, "Rust bindings for Debugger API",
pointing folks at the discussion in bug 1263317 about adding a Rust API for
SpiderMonkey's debugging facilities. Since then we've learned two
interesting things:

First: Because of the way Rust crates are compiled and linked, it's
difficult to have one Rust API (rust-mozjs) located in a separate crate,
and another Rust API (for the debugger) located in js/src, as originally
discussed. Everything would be much easier if there could be a single crate
providing Rust bindings for the SpiderMonkey library. (Anthony, could you
follow up with more details here?)

Second: Servo is finding their periodic updates to the latest SpiderMonkey
to require exorbitant amounts of work. At present, an engineer needs to
dedicate an entire quarter to it, which is completely untenable. Having the
Rust API be treated as just another build and test in SpiderMonkey's
ordinary CI processes would be a huge improvement: problems could be
addressed as they arise.

This would be a new responsibility SpiderMonkey would be taking on. The
Devtools faction (me, Nick Fitzgerald, and Eddy Bruel) will be on the hook
to keep it alive, and since Servo will be dependent on it, you can expect
full support from that side as well. And the SpiderMonkey team proper has a
few Rust fans itself.

So, is this something SpiderMonkey is willing to take on?
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals

Reply via email to