Improve performance of SharingStarted.StartedLazily by changing flow to unsafeFlow #4393
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.
In this case,
StartLazily
usesflow
, but since it simply collectssubscriptionCount
and processes it, there is no need to use SafeFlow and consume additional resources for context checks.In other words, because it only collects data from another Flow and passes it along without executing any custom logic which switches coroutine context(similar to operators like
map
orfilter
), it can useunsafeFlow
to skip context checks and reduce computing resource usage.