This repository was archived by the owner on Feb 25, 2025. It is now read-only.
iOS: Eliminate strong retain loop in Scenario tests #56249
Merged
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.
FlutterViewControllerTest testDrawLayercreated a callback which strongly referenced itself in its own body as part of an asynchronous recursive loop. The recursion was unnecessary and the test consistently passes, even if run on repeat > 100 times without it.Now that there's only one call, eliminates the unnecessary local and inlines it into the
dispatch_aftercall.This was originally introduced in #50072.
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.