-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Add TcpListener::into_incoming and IntoIncoming #88339
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Mark-Simulacrum (or someone else) soon. Please see the contribution instructions for more information. |
This comment has been minimized.
This comment has been minimized.
Seems reasonable to me. This needs to be marked as unstable, though, with a tracking issue added. Once that's done and CI passes, r=me. |
How should I name the feature? |
That sounds good to me. |
The `incoming` method is really useful, however for some use cases the borrow this introduces is needlessly restricting. Thus, an owned variant is added.
@bors r+ |
📌 Commit ced597e has been approved by |
⌛ Testing commit ced597e with merge d84c304805116ba715faa71e9992e3d3682494ac... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
I don't really understand the error message :( |
⌛ Testing commit ced597e with merge 3ccc225e2a438726b9e5bdcbe4fa239160a86376... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@joshtriplett Can you please help me out on the CI failure? I don't fully understand the logs, but it doesn't look like my commit is causing this |
Add TcpListener::into_incoming and IntoIncoming The `incoming` method is really useful, however for some use cases the borrow this introduces is needlessly restricting. Thus, an owned variant is added. r? `@joshtriplett`
Rollup of 10 pull requests Successful merges: - rust-lang#86382 (Make diagnostics clearer for `?` operators) - rust-lang#87529 (Fix ICE in `improper_ctypes_definitions` lint with all-ZST transparent types) - rust-lang#88339 (Add TcpListener::into_incoming and IntoIncoming) - rust-lang#88735 (Don't lint about missing code examples in derived traits) - rust-lang#88751 (Couple of changes to FileSearch and SearchPath) - rust-lang#88883 (Move some tests to more reasonable directories - 7) - rust-lang#88887 (Const Deref) - rust-lang#88911 (Improve error message for type mismatch in generator arguments) - rust-lang#89014 (PassWrapper: handle separate Module*SanitizerPass) - rust-lang#89033 (Set the library path in sysroot-crates-are-unstable) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Export `tcp::IntoIncoming` Added in rust-lang#88339 but not publicly exported.
Export `tcp::IntoIncoming` Added in rust-lang#88339 but not publicly exported.
Export `tcp::IntoIncoming` Added in rust-lang#88339 but not publicly exported.
/// Ok(()) | ||
/// } | ||
/// ``` | ||
#[unstable(feature = "tcplistener_into_incoming", issue = "88339")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tracking issue number here refers to this PR itself. Did something go wrong? Is there an actual tracking issue for this feature?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tracking issue is #88373, so this likely was a mistake
…coming_issue_number, r=workingjubilee Fix issue number for the `tcplistener_into_incoming` feature As per [this comment](rust-lang#88339 (comment)), the issue number for the `tcplistener_into_incoming` feature is the one of the PR that implements it instead of the tracking issue. - rust-lang#88339 - rust-lang#88373
Rollup merge of rust-lang#126783 - tguichaoua:fix_tcplistener_into_incoming_issue_number, r=workingjubilee Fix issue number for the `tcplistener_into_incoming` feature As per [this comment](rust-lang#88339 (comment)), the issue number for the `tcplistener_into_incoming` feature is the one of the PR that implements it instead of the tracking issue. - rust-lang#88339 - rust-lang#88373
The
incoming
method is really useful, however for some use cases the borrowthis introduces is needlessly restricting. Thus, an owned variant is added.
r? @joshtriplett