Resources can only wait for type erased events
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 107
- Forks
- 26
- Avg merge
- 8d 11h
- Merged PRs (30d)
- 2
Description
Currently you have to create a type erased event in order to have a resource wait_for it. Does it make sense to allow resources to wait_for their own event type to avoid this, maybe even wait_for another resource of their own type as syntactic sugar?
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 resource wait_for and type-erased event APIs in the C++ library. Determine whether waiting on a resource's own event type or another resource can be specified unambiguously, then document the chosen behavior and add the relevant coverage once the API is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100