Tracking Issue for unix_socket_exclbind
Open
Nobody has claimed this yet.
C-tracking-issue
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(unix_socket_exclbind)]
This is a tracking issue for the unix_socket_exclbind feature.
Allows the socket to be set in exclusive binding mode to avoid another connection to bind even thought it might have been set with SO_REUSEADDR prior.
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 with the #![feature(unix_socket_exclbind)] gate and the socket behavior described here. Determine the implementation, stabilization requirements, and tests needed to verify exclusive binding against SO_REUSEADDR; done when the tracking issue's requirements are resolved.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100