why does memmap2::Mmap::map need to be unsafe?

[dev-ardi]

Most other ffi wrappers provide a safe interface. Why is this unsafe?

[RazrFalcon]

Can you list those wrappers?

To be safe in Rust terms, a memory chunk must have a single owner. Which is not possible with memmap, since anyone can modify the mapped file.

[dev-ardi]

I'm not talking about mmap wrappers, I'm talking about general libc wrappers.

This makes sense, is that in the docs? Did I miss it?

[RazrFalcon]

https://docs.rs/memmap2/latest/memmap2/struct.Mmap.html#safety ?

[dev-ardi]

Ah that's great. It would be nice to add a link to that section in all unsafe APIs.