Alan Somers
Alan Somers
This PR sacrifices a little bit of type safety in order to build successfully with both old and new versions of libc. I'm not sure if we should merge it,...
I've never gotten into the habit of using any of those. But I'd be willing to give it a try for Nix.
> > Would this PR fix #2071 ? > > I think so, can you test it? No, I can't. I don't have an Illumos system. Maybe @nospam3089 can test...
> poll could usefully take &mut [Option]? Sounds good to me too
I don't understand what problem this PR would solve. Could you please explain?
> The only way to ensure it is initialized when returning from `recvmsg` is to either: > > * initialize it before calling `recvmsg` > > * write "bad" bytes...
I can see the value of this PR; it allows something to be done safely that was previously only possible unsafely. It also avoids the problem that the existing `sigaction`...
To define two enum values that have the same representation, create a constant instead. See `SockProtocol::CanRaw` for an example.
Unless this can violate some other invariant of SockaddrIn, it isn't unsound. I assume you're referring to the unsoundness that results from reading uninitialized memory? In this case, though the...
We shouldn't need to zero it first. As far as the compiler is concerned, that FFI call always initializes the return argument. We should just check the sin_family field, the...