Skip to content

⚡ Bolt: Optimize hasSelection and selectedSize computed properties#310

Closed
acebytes wants to merge 1 commit into
mainfrom
bolt/optimize-has-selection-14428856092354118071
Closed

⚡ Bolt: Optimize hasSelection and selectedSize computed properties#310
acebytes wants to merge 1 commit into
mainfrom
bolt/optimize-has-selection-14428856092354118071

Conversation

@acebytes

Copy link
Copy Markdown
Contributor

💡 What: Optimized hasSelection to use .contains(where:) instead of checking .isEmpty on selectedResults (which creates a filtered array). Optimized selectedSize to use .lazy.filter to bypass intermediate array allocation.
🎯 Why: To prevent unnecessary full array allocations and O(N) traversals on every UI re-render when SwiftUI evaluates these computed properties.
📊 Impact: Reduces memory churn and intermediate array allocations during SwiftUI view updates, speeding up the render loop.
🔬 Measurement: Verify memory allocations and CPU usage drop during UI interactions (checking/unchecking items) and ensure UI responsiveness is maintained.


PR created automatically by Jules for task 14428856092354118071 started by @acebytes

💡 What: Optimized `hasSelection` to use `.contains(where:)` instead of checking `.isEmpty` on `selectedResults` (which creates a filtered array). Optimized `selectedSize` to use `.lazy.filter` to bypass intermediate array allocation.
🎯 Why: To prevent unnecessary full array allocations and O(N) traversals on every UI re-render when SwiftUI evaluates these computed properties.
📊 Impact: Reduces memory churn and intermediate array allocations during SwiftUI view updates, speeding up the render loop.
🔬 Measurement: Verify memory allocations and CPU usage drop during UI interactions (checking/unchecking items) and ensure UI responsiveness is maintained.

Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@acebytes

Copy link
Copy Markdown
Contributor Author

Closing as duplicate. The Bolt bot has opened many PRs for the same lazy-filter / short-circuit / array-allocation optimizations in CacheoutViewModel.swift and MenuBarView.swift / CleanConfirmation.swift. Consolidating on #393 as the canonical (most recent iteration).

@acebytes acebytes closed this Jun 16, 2026
@google-labs-jules

Copy link
Copy Markdown
Contributor

Closing as duplicate. The Bolt bot has opened many PRs for the same lazy-filter / short-circuit / array-allocation optimizations in CacheoutViewModel.swift and MenuBarView.swift / CleanConfirmation.swift. Consolidating on #393 as the canonical (most recent iteration).

Understood. Acknowledging that this PR is a duplicate and stopping work on this task.

@acebytes acebytes deleted the bolt/optimize-has-selection-14428856092354118071 branch June 16, 2026 04:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant