Check the safety of Rust crate seq_lock
Rust crate seq_lock has unsafe code to attempt reading the value of type T
wrapped by a SeqLock<T>
while concurrent writes can take place. The safety of this code should be checked since it is UB to just create a value of type T
by reading memory with concurrent writes.
-
Write test cases and run them with MIRI -
Consider using MaybeUninit
until it is sure that no concurrent write has taken place
Edited by RILLING Louis