Tracking Issue for tcplistener_into_incoming · Issue #88373 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

Feature gate: #![feature(tcplistener_into_incoming)]

This is a tracking issue for #88339

The TcpListener::incoming method is really useful, however for some use cases the borrow it introduces is needlessly restricting. Thus, an owned variant is added.

Public API

// std::net

pub struct IntoIncoming;

impl Iterator<Item = io::Result> for IntoIncoming;

impl TcpListener { pub fn into_incoming(self) -> IntoIncoming; }

Steps / History

• Implementation: Add TcpListener::into_incoming and IntoIncoming #88339
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• The IntoIncoming could provide methods that allow access to (or getting back) the TcpListener. I decided against it, but they could be added if there is a use case
• IMO the into_incoming method should return an opaque impl IntoIterator so that IntoIncoming is not public API, but that would be inconsistent with the rest of std.