mopinion: Clarify coio_call usage
Open
Nobody has claimed this yet.
c api
dev
reference
server
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
https://app.mopinion.com/dashboard/inbox/detail/2994263
в каком случае нужно использовать coio_call, а в каком -- не нужно? чтение из O_NONBLOCK сокета нужно оборачивать в coio_call ?
https://www.tarantool.io/ru/doc/2.3/dev_guide/reference_capi/coio/
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 linked coio C API documentation and the referenced Russian question. Determine where the documentation explains coio_call and nonblocking socket reads, then clarify when coio_call is required and whether O_NONBLOCK reads need it. Done means the usage guidance answers both questions unambiguously.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100