writev_at should not be marked safe
Hi! I was reviewing the contents of this crate and noticed that writev_at
has a safety requirement but is marked safe. As iovec
is a public struct, I believe this is incorrect usage of unsafe Rust and users of this crate can cause unsoundness in safe code.
I think there are two ways to fix this: either it gets marked unsafe, or it accepts some safe wrapper around iovec
s. I'll note that the one usage of this function in this crate uses &[VolatileSlice]
which seems perfectly fine as a safe input type.