Transmuting to static mut reference: Is it correct?

[Nugine]

I cannot find any safety comments here.

rspack/crates/node_binding/src/plugins/mod.rs

Lines 39 to 59 in 2f7ffb5

	async fn compilation(
	&mut self,
	args: rspack_core::CompilationArgs<'_>,
	) -> rspack_core::PluginCompilationHookOutput {
	if self.is_hook_disabled(&Hook::Compilation) {
	return Ok(());
	}
	let compilation = JsCompilation::from_compilation(unsafe {
	std::mem::transmute::<&'_ mut rspack_core::Compilation, &'static mut rspack_core::Compilation>(
	args.compilation,
	)
	});
	self
	.compilation_tsfn
	.call(compilation, ThreadsafeFunctionCallMode::NonBlocking)
	.into_rspack_result()?
	.await
	.map_err(|err| internal_error!("Failed to call compilation: {err}"))?
	}

[h-a-n-a]

This is considered to be safe under the compilation call from the JavaScript side. But It is not a safe if you are trying to cache the compilation and reuse it after any rebuilds, which would cause some potential segmentation faults.

[h-a-n-a]

Feel free to come up with a PR to describe this SAFETY contract. We would be much appreciated :)