Allow library code to detect the JoinableTaskContext is not associated with Main thread #1477
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
…th main thread It allows library code to skip certain work under such conditions. For example to build an extensive dependency graph for dataflow dependencies, or dependencies in work queues.
AArnott
approved these changes
Jul 16, 2025
Co-authored-by: Andrew Arnott <[email protected]>
AArnott
approved these changes
Jul 16, 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.
It allows library code to skip certain work under such conditions. For example to build an extensive dependency graph for dataflow dependencies, or dependencies in work queues.
The name of the property is based on an existing CreateNoOpContext method in the same class.
It is added because a library running inside both environments with and without UI thread becomes more important over the time, we want better way to optimize under both context.
Potentially, we can do further work in the JTF library itself, to reduce some data structure maintenance, because SwitchToMainThread is always non-op under such condition. For example, nestingFactories might not be maintained as it would never post any request to the factory etc.