cameron314 / cameron314/concurrentqueue
Why not provide the wait_enqueue API? Is there any difficulty?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.5k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
When I use blockingconcurrentqueue , I notice that the wait_enqueue API is not provided, which will blocks when it find no space.
What I want to know is, are we not implementing the API because of any difficulties or is it difficult to implement the API in the current implementation?
Contributor guide
No contributing guide indexed for this repository
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 locating the blockingconcurrentqueue implementation and its existing enqueue and wait-related APIs. Determine whether a blocking wait_enqueue operation has a defined behavior when the queue is full, and treat a clear feasibility decision or an accepted API specification as the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100