refactor: change reader's get_range result to be a static future #5755
+208
−160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first in a set of PRs to add both a new scheduler implementation (a lightweight task-free scheduler) and a new reader implementation (that utilizes I/O uring).
The need for this isn't terribly obvious. Instead of...
it would seem we could just do...
...and we will have a static future. Unfortunately, the latter approach changes the semantics somewhat. Instead of calling get_range immediately, it does not call get_range until the future is first polled. This is a problem for the I/O uring reader which needs to immediately push the request into the submission queue (and not wait until polled). Perhaps there is a different solution than this PR but this PR is also not too onerous and does work.
This PR was partially created with Claude Opus 4.5. I have reviewed all suggested changes and take full responsibility for them.