Tracking Issue for {IpAddr, SocketAddr}::unspecified_from()
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
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: rust-lang/libs-team#823
- Implementation: #160905
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- Spelling of function (
unspecified_fromvsto_unspecifiedvs 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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the core::net API and the implementation referenced as #160905. Review the unresolved questions about the function spelling, receiver form, and SocketAddrV6 flowinfo and scope_id handling; this tracking issue is done when those questions are resolved and the remaining FCP and stabilization steps are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100