Documentation for Heap::handle is unclear

[jdm]

mozjs/mozjs-sys/src/jsgc.rs

Lines 333 to 348 in d6c3bd9

	/// Retrieves a Handle to the underlying value.
	///
	/// # Safety
	///
	/// This is only safe to do on a rooted object (which Heap is not, it needs
	/// to be additionally rooted), like RootedGuard, so use this only if you
	/// know what you're doing.
	///
	/// # Notes
	///
	/// Since Heap values need to be informed when a change to underlying
	/// value is made (e.g. via `get()`), this does not allow to create
	/// MutableHandle objects, which can bypass this and lead to crashes.
	pub unsafe fn handle(&self) -> JS::Handle<T> {
	JS::Handle::from_marked_location(self.ptr.get() as *const _)
	}

I no longer remember when "if you know what you're doing applies", but we have a lot of usages in Servo which makes me nervous.

[sagudev]

IIUC this is only safe when done on RootedGuard<Heap<T>> (or similar, something that ensures that heap is rooted), so we could just do

impl RootedGuard<Heap<T>> {
pub fn handle(&self) -> JS::Handle<T> { 
         JS::Handle::from_marked_location(self.ptr.get() as *const _) 
     } 
}

[Redfire75369]

From my understanding, it's also safe if you have any Heap<T>, as long as it's traced, eg via a custom trace op or a global tracer.