Expected error return codes not defined
Open
mirrored
- Dominant language
- C
- Stars
- 3
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The majority of the api function calls return 'socket_error_t' however there is no documentation that states what the expected error codes for each function should be under particular error conditions.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the API function declarations that return socket_error_t and the definitions of the error codes. Review each function's documented error conditions and record the expected code for every case. Done means the API documentation consistently specifies these return codes; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100