[Optimize] Enable SwiftUI's LogForEachSlowPath by default in debug builds#2350
Merged
Dimillian merged 1 commit intoDimillian:mainfrom Oct 21, 2025
Merged
Conversation
jesusjimsa
pushed a commit
to jesusjimsa/IceCubesApp
that referenced
this pull request
Nov 28, 2025
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
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.
Always enable SwiftUI's LogForEachSlowPath in debug builds.
Summary
SwiftUI's ForEach documentation states that we can enable such log by adding
-LogForEachSlowPath YESin launch arguments.It is equivalent to set UserDefaults since the SwiftUI Runtime is always using UserDefaults to check it.
This PR makes this feature default to true in debug builds.
To disable such log, append
-LogForEachSlowPath NOin launch arguments or simply comment out the added code.Result
When hitting a slow path for
ForEach, a warning log will be emitted and then we may consider taking some actions to fix it to improve render performance.Currently, I have found one for the
Array<Action>data. A potential fix PR may be submitted later.