Hacker News new | ask | show | jobs
by Quarrel 198 days ago
Thank you.

I assumed this was what was happening, but conflating network layer protocols with transport layer ones isn't great.

I'm surprised that pedantic zealots, like me in my youth, haven't risen up and flooded rust with issues over it way before this though.
1 comments
knorker 198 days ago
Why are you saying rust needs to be flooded with issues? Rust isn't conflating transport layers and protocols. OP is.

UdpSocket is just able to take ANY file descriptor and try to use it as if it's a UDP socket.

E.g. this compiles, and it's not a bug. It doesn't make any sense, but it's not a bug:

    fn main() {
        let f = std::fs::File::open("/dev/null").unwrap();
        let f: std::os::fd::OwnedFd = f.into();
        let socket: std::net::UdpSocket = f.into();
    }
OP is clearly confused, since there's no need to do this at all. socket2::Socket already has a `send_to()`: https://docs.rs/socket2/latest/socket2/struct.Socket.html#me...

I think OP either banged on this until it compiled, maybe blindly copying from other examples, or it's vibe coded, and shows why AI needs supervision from someone who can actually understand what the code does.

link