Tracking issue for udp_peer_addr

[LinusU]

Tracking issue for making peer_addr() on UdpSocket stable: #59106, #59104

[sanxiyn]

FYI, in Rust issue tracker, "tracking issue" is a jargon for stabilizing features already in nightly. As I understand, peer_addr is not yet in nightly?

[jonas-schievink]

@sanxiyn A tracking issue has to be opened before a feature can land in nightly, because the #[unstable] attribute needs an issue number to refer to. #59106 has also been approved already, so it'll land in one of the next nightlies.

[MOZGIII]

How about moving this to stable?

[ghedo]

What's left to do to stabilize this feature? Any ETA?

[Thomasdezeeuw]

Can this be stablised for 1.37?

Another reminder -- can we kick off FCP for stabilization?

[Dylan-DPC-zz]

@rust-lang/libs any updates?

[sfackler]

@rfcbot fcp merge

[rfcbot]

Team member @sfackler has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Amanieu
• @Kimundi
• @SimonSapin
• @alexcrichton
• @dtolnay
• @sfackler
• @withoutboats

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.