[Observation] Ensure deinitialized Observable types don't leave active observations in memory #82752
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.
Explanation:
This ensures a potential leak with SwiftUI and other systems using Observation do not leak observation closures when the potential Observable instances used are only weakly referenced inside the tracking closure.
Scope:
This is limited to the runtime behavior of Observable types and has no ABI or language level interactions.
Issues:
rdar://112167556
Original PRs:
#79823
#82307
Risk:
Low - This is very targeted to just Observation, however it is a behavioral change which does not make this a zero risk change.
Testing:
New unit tests were added to catch at least some of the potential cases this issue can occur with.