Cross-memory model data
e9c94b8
Opened by Lars Bergstrom at
In our current model, any time that we return a JS object to Rust, we carefully thread in some Rust code that ensures the JS GC adds it to the root set and unregister it when Rust drops the value.
The ultimate goal would be for the Rust compiler to generate stack / register maps for JS-owned values so that the JS GC can directly walk the Rust stack. This would eliminate the need for explicit rooting and would reduce constraints on JS GC implementation.
CC: @zwarich @pcwalton
This issue has been moved to the RFCs repo: rust-lang/rfcs#318
Rust highfive robot at 2014-09-24 05:03:46