Tracking Issue for {IpAddr, SocketAddr}::unspecified_from()

Feature gate: #![feature(addr_unspecified_from)]

This is a tracking issue for the IpAddr::unspecified_from() and SocketAddr::unspecified_from() functions for creating a 0.0.0.0:0/[::]:0 address matching the IP version of the input.

Public API

// core::net

impl IpAddr {
    pub fn unspecified_from(this: Self) -> Self;
}

impl SocketAddr {
    pub fn unspecified_from(this: Self) -> Self;
}

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

ACP: ACP: IpAddr::to_unspecified() and SocketAddr::to_unspecified() libs-team#823
Implementation: implement <IpAddr, SocketAddr>::unspecified_from() #160905
Final comment period (FCP)¹
Stabilization PR

Unresolved Questions

Spelling of function (unspecified_from vs to_unspecified vs something else), and whether we allow the function to take (&self) instead of (this: Self).
How should the flowinfo and scope_id fields of SocketAddrV6 be handled - inherited or zeroed?

https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

Rollup merge of rust-lang#160905 - malezjaa:imlpement-addr-unspecifie…

Unrolled build for #160905

Rollup merge of #160905 - malezjaa:imlpement-addr-unspecified-from, r…

Navigation Menu

Repository navigation

Tracking Issue for {IpAddr, SocketAddr}::unspecified_from() #158975

Public API

Steps / History

Unresolved Questions

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Tracking Issue for {IpAddr, SocketAddr}::unspecified_from() #158975

Description

Public API

Steps / History

Unresolved Questions

Footnotes

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions