✨ Support awaiting futures across different contexts#94
Merged
Conversation
Allow coroutines running on one context to await futures created on another context. While awaiting, the consuming context delegates its state and sleep time to the producer context, enabling proper scheduler behavior across context boundaries. When the producer completes, the consumer resumes and receives the value, with all memory properly cleaned up. This enables more flexible async patterns where work can be distributed across multiple execution contexts. Note that is is an anti-pattern and not a desirable usage of async context. This change fills a hole that would otherwise be UB into something with clear semantics. Includes comprehensive tests covering normal completion, exception propagation, cancellation, and state delegation across contexts. Resolves #93
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Allow coroutines running on one context to await futures created on another context. While awaiting, the consuming context delegates its state and sleep time to the producer context, enabling proper scheduler behavior across context boundaries.
When the producer completes, the consumer resumes and receives the value, with all memory properly cleaned up. This enables more flexible async patterns where work can be distributed across multiple execution contexts.
Note that is is an anti-pattern and not a desirable usage of async context. This change fills a hole that would otherwise be UB into something with clear semantics.
Includes comprehensive tests covering normal completion, exception propagation, cancellation, and state delegation across contexts.
Related Issue
Resolves #93
Test Plan
conan create .