⚡ Bolt: Optimize SwiftUI computed properties memory churn#299
Conversation
Replaced eager array filtering with `.lazy.filter` and `.contains(where:)` in frequently evaluated SwiftUI computed properties. SwiftUI evaluates computed properties on every state change and render pass. Eagerly filtering arrays (`filter`) causes continuous intermediate array allocations leading to memory churn. Eliminates O(N) array allocations during property access. Reduces UI stuttering by improving memory efficiency. Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Closing as duplicate. The Bolt bot has opened many PRs for the same lazy-filter / short-circuit / array-allocation optimizations in |
Understood. Acknowledging that this PR is being closed as a duplicate in favor of #393, and stopping work on this task. |
.lazy.filterand.contains(where:)in frequently evaluated SwiftUI computed properties.filter) causes continuous intermediate array allocations leading to memory churn.PR created automatically by Jules for task 3804638611253282619 started by @acebytes