unsafe use of pointer to object on stack

[JakkuSakura]

kanal/src/lib.rs

Line 191 in f3c2bf1

let mut sig = SyncSignal::new(&mut data as *mut T, std::thread::current());

Here data is taken pointer from, then forgotten. However, data is on stack, so it can be corrupted when being read again. Do you have justification for this?

In Golang this is safe, as Golang performs escape analysis, and any object taken references from and escapes are actually allocated to heap with GC. But in Rust it is not.

[JakkuSakura]

Ok, I read the code of the Receiver side. The Sender will not leave the function when the Receiver reads out the value. So data will remain valid then

[fereidani]

Yes, it's true, so it's not UB.