Specify behavior of functions taking `ToSockAddrs`

[tbu-]

Examples of such functions inclde UdpSocket::bind and UdpSocket::send. Is the first address taken, the last, are all addresses taken into consideration...

[steveklabnik]

I'm not 100% sure what this is asking, can you elaborate a bit, please?

[alexcrichton]

Functions that take T: ToSocketAddrs in the std::net module take an object which will be converted to any number of actual SocketAddr types. It's not currently clear what these methods do when there are multiple socket addresses that are resolved to.

For example, TcpStream::connect will attempt to connect to each address in turn (returning the first that succeeds), but UdpSocket::send will only send a datagram to the first address. Furthermore, there are questions like should TcpListener::bind bind to all the addresses or just one?

[steveklabnik]

Is the current behavior the correct one? IE, do we even want to make that guarantee?

[tbu-]

You could say what it does right now with a remark that it's not stabilized yet.

[steveklabnik]

I'm removing the 'docs' tag until we decide what we want to specify here.

[tbu-]

@steveklabnik Can you also remove the 'easy' tag?

[Aatch]

Is this still relevant? I don't think we change anything related in a backwards-compatible way.

[alexcrichton]

This is basically just a docs thing now, we need to be sure we specify what happens if multiple addresses are returned.