3 ms·

That happens when someones learning project ("I rewrite a library in the new language I want to learn") ends up in productive code.

• IshKebab 11mo ago
  This is in the standard library; it's not a learning project. And it also isn't even incorrect - see erk__'s comment. Rust is an excellent language and fully capable of production use.
  • Sharlin 11mo ago
    It's not, it's the `socket2` library. The standard sockets don't allow (ab)using actual `UdpSocket`s as a different kind of datagram socket.
    • IshKebab 11mo ago
      We're talking about UdpSocket: https://doc.rust-lang.org/stable/std/net/struct.UdpSocket.html https://doc.rust-lang.org/stable/std/net/struct.UdpSocket.ht...
      • Sharlin 11mo ago
        Yes, I know, but the point is that the standard UdpSocket is correctly named as it doesn’t represent any other datagram socket. Uh, we’re pribably in agreement here actually.
        • IshKebab 11mo ago
          Yeah exactly! :-D
    • knorker 11mo ago
      Sure it does. let f = std::fs::File::open("/dev/null").unwrap(); let f: std::os::fd::OwnedFd = f.into(); let socket: std::net::UdpSocket = f.into(); This is really no different. In this example it's not even a socket.