Clarify the behavior of UDP sockets wrt. multiple addresses in connect#44388
Clarify the behavior of UDP sockets wrt. multiple addresses in connect#44388bors merged 1 commit intorust-lang:masterfrom
connect#44388Conversation
|
r? @BurntSushi (rust_highfive has picked a reviewer for you, use r? to override) |
| /// Unlike in the TCP case, passing an array of addresses to the `connect` | ||
| /// function of a UDP socket is not a useful thing to do: The OS will be | ||
| /// unable to determine whether something is listening on the remote | ||
| /// address without the application sending data. |
There was a problem hiding this comment.
since this is no longer associated with an example, seems like we can move this paragraph above the # Examples heading. what do you think?
There was a problem hiding this comment.
My rationale for leaving it there was that this explanation is in a similar spot for the other methods and also in TcpStream. But I guess I can move it up.
There was a problem hiding this comment.
Actually, the text is already up there. It's just summarized in the examples because there's usually an example of using multiple addresses.
|
@bors r+ rollup |
|
📌 Commit b4d0f61 has been approved by |
…=frewsxcv Clarify the behavior of UDP sockets wrt. multiple addresses in `connect` CC @frewsxcv rust-lang#22569 rust-lang#44209
…=frewsxcv Clarify the behavior of UDP sockets wrt. multiple addresses in `connect` CC @frewsxcv rust-lang#22569 rust-lang#44209
|
This seems fine to me. It might be worth noting that these docs appear to be strengthening the contract of |
…=frewsxcv Clarify the behavior of UDP sockets wrt. multiple addresses in `connect` CC @frewsxcv rust-lang#22569 rust-lang#44209
…=frewsxcv Clarify the behavior of UDP sockets wrt. multiple addresses in `connect` CC @frewsxcv rust-lang#22569 rust-lang#44209
…=frewsxcv Clarify the behavior of UDP sockets wrt. multiple addresses in `connect` CC @frewsxcv rust-lang#22569 rust-lang#44209
CC @frewsxcv #22569 #44209