Repository navigation
Release consumed Just values from nested subscriptions - #65
Merged
Merged
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
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.
Removing a feature from the device's array could leave it retained by the consumed
AsyncJustSequenceiterator inside an active nestedflatMapLatestsubscription. The iterator now clears its stored value when consumed or cancelled, while iterator copies continue sharing one consumption state.Adds the issue's nested subscription regression: the removed feature deallocates while its inner subject continues delivering values. Documents that array removal does not cancel a subscription and that the consuming task still needs an owner.
Validation: reproduced the regression before the fix; all 173 tests pass on Swift 6.4/macOS. Existing unused throwing-task warnings remain in unrelated tests.
Fixes #35.