Is passing an invalid pointer to recv sound?

https://github.com/bytecodealliance/system-interface/blob/8ee8c825df4c183f06d48ec5d10556a5bf11655b/src/io/is_read_write.rs#L141-L152

https://learn.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-recv doesn't say anything about this, this seems sketchy.

Read src/io/is_read_write.rs at lines 141-152 and compare the pointer handling with the linked Windows recv contract. Determine whether passing an invalid pointer is sound for this interface, then identify the expected behavior or documentation needed to resolve the concern; the issue does not name a test or a specific fix.

Vom Indexierungsmodell aus dem Issue-Text verfasst.