Use type_info in equality comparison of any_scheduler
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 39
Description
Currently, we compare pointers to vtable objects in static storage duration to determine if the underlying scheduler types are equal. I think, that is not correct.
Instead we should use something like type_info.
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 at the any_scheduler equality comparison and inspect how it currently compares pointers to vtable objects in static storage. Determine how type_info should represent equality of the underlying scheduler types, then verify the behavior against the existing scheduler-related coverage; done means equal scheduler types no longer depend on vtable pointer identity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100