alibaba / alibaba/async_simple
Refactoring IOExecutor
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 316
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
### Search before asking
- [ ] I searched the [issues](https://github.com/alibaba/async_simple/issues) and found no similar issues.
### What happened + What you expected to happen
Current IOExecutor has `linux-aio` related interface
We hope to remove platform level api at IOExecutor base class, make IOExecutor become empty class
And we can implement `UringExecutor, AsioExecutor`, and the other user defined IOExecutor based on IOExecutor
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the IOExecutor interface and its linux-aio-related API, then compare the intended UringExecutor and AsioExecutor implementations. Map which platform-level responsibilities belong in each executor. Done means IOExecutor is empty while platform-specific and user-defined executors remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100