types: Use ThreadChannel
and AnyThreadChannel
consistently
#10181
+31
−22
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.
Please describe the changes this PR makes and why it should be merged:
I've been having issues with some methods returning
ThreadChannel
and some returningAnyThreadChannel
. This PR makes how we use each consistent.ThreadOnlyChannel
will always bePublicThreadChannel<true>
), that is used.AnyThreadChannel
type.ThreadChannel
type. Typically, the user shouldn't have to useThreadChannel
in their codebase at all (since all userland-facing values have been changed toAnyThreadChannel
), but it doesn't hurt to allow it here.Status and versioning classification: