-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify behavior of functions taking ToSockAddrs
#22569
Comments
I'm not 100% sure what this is asking, can you elaborate a bit, please? |
Functions that take For example, |
Is the current behavior the correct one? IE, do we even want to make that guarantee? |
You could say what it does right now with a remark that it's not stabilized yet. |
I'm removing the 'docs' tag until we decide what we want to specify here. |
@steveklabnik Can you also remove the 'easy' tag? |
Is this still relevant? I don't think we change anything related in a backwards-compatible way. |
This is basically just a docs thing now, we need to be sure we specify what happens if multiple addresses are returned. |
Moving to p-high and assigning myself; i'd like to get this resolved in the next release cycle. |
…xamples, r=QuietMisdreavus Rewrite `std::net::ToSocketAddrs` doc examples. in particular: * show how to create an iterator that yields multiple socket addresses * show more failing scenarios done this as preliminary work while investigating rust-lang#22569 note: i haven't run doc tests on my machine for this, so would be good to confirm CI passes before approving
…xamples, r=QuietMisdreavus Rewrite `std::net::ToSocketAddrs` doc examples. in particular: * show how to create an iterator that yields multiple socket addresses * show more failing scenarios done this as preliminary work while investigating rust-lang#22569 note: i haven't run doc tests on my machine for this, so would be good to confirm CI passes before approving
…xamples, r=QuietMisdreavus Rewrite `std::net::ToSocketAddrs` doc examples. in particular: * show how to create an iterator that yields multiple socket addresses * show more failing scenarios done this as preliminary work while investigating rust-lang#22569 note: i haven't run doc tests on my machine for this, so would be good to confirm CI passes before approving
…xamples, r=QuietMisdreavus Rewrite `std::net::ToSocketAddrs` doc examples. in particular: * show how to create an iterator that yields multiple socket addresses * show more failing scenarios done this as preliminary work while investigating rust-lang#22569 note: i haven't run doc tests on my machine for this, so would be good to confirm CI passes before approving
…xamples, r=QuietMisdreavus Rewrite `std::net::ToSocketAddrs` doc examples. in particular: * show how to create an iterator that yields multiple socket addresses * show more failing scenarios done this as preliminary work while investigating rust-lang#22569 note: i haven't run doc tests on my machine for this, so would be good to confirm CI passes before approving
…xamples, r=QuietMisdreavus Rewrite `std::net::ToSocketAddrs` doc examples. in particular: * show how to create an iterator that yields multiple socket addresses * show more failing scenarios done this as preliminary work while investigating rust-lang#22569 note: i haven't run doc tests on my machine for this, so would be good to confirm CI passes before approving
Opened a PR for this: #44209 |
…ios, r=alexcrichton Expand docs of multi-address behavior of some UDP/TCP APIs. Fixes rust-lang#22569.
…ios, r=alexcrichton Expand docs of multi-address behavior of some UDP/TCP APIs. Fixes rust-lang#22569.
…=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
…=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
Examples of such functions inclde
UdpSocket::bind
andUdpSocket::send
. Is the first address taken, the last, are all addresses taken into consideration...The text was updated successfully, but these errors were encountered: