Adds spawn_in_scope
#4394
Open
Adds spawn_in_scope
#4394
Conversation
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
jprider63
added a commit
to jprider63/ossa
that referenced
this pull request
Aug 1, 2025
jprider63
added a commit
to jprider63/ossa
that referenced
this pull request
Aug 3, 2025
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.
This adds the function
spawn_in_scopewhich spawns a future with the scope provided by the user. I needed this since I have aSignalat a given scope (created withSignal::new_maybe_sync_in_scope_with_caller) that is periodically updated by an associated future.spawn_foreverdid not work since the root scope in the future would attempt to update the subscope's Signal.Note: This PR is on the
v0.6branch so you might want to upstream it tomaintoo.