coroutine: remove remnants of variadic futures #2066
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Coroutine support still contains some remnants of variadic futures;
remove them to simplify the code.
The `awaiter` struct had three specializations, one for void, one
for one template parameter, and one for {zero, two+} parameters.
The first two remain.
without_preemption_check() also had three specializations, only one
remains.
graphcareful
pushed a commit
to graphcareful/seastar
that referenced
this pull request
Mar 20, 2024
Coroutine support still contains some remnants of variadic futures;
remove them to simplify the code.
The `awaiter` struct had three specializations, one for void, one
for one template parameter, and one for {zero, two+} parameters.
The first two remain.
without_preemption_check() also had three specializations, only one
remains.
Closes scylladb#2066
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Coroutine support still contains some remnants of variadic futures; remove them to simplify the code.
The
awaiterstruct had three specializations, one for void, one for one template parameter, and one for {zero, two+} parameters. The first two remain.without_preemption_check() also had three specializations, only one remains.