Skip to content

⚡ Bolt: [performance improvement] Short-circuit evaluation and prevent intermediate array allocations#284

Closed
acebytes wants to merge 1 commit into
mainfrom
bolt-performance-improvement-6607650057219304508
Closed

⚡ Bolt: [performance improvement] Short-circuit evaluation and prevent intermediate array allocations#284
acebytes wants to merge 1 commit into
mainfrom
bolt-performance-improvement-6607650057219304508

Conversation

@acebytes

Copy link
Copy Markdown
Contributor

💡 What: Replaced eager .isEmpty checks on filtered collections with early-exiting .contains(where:) in hasSelection, and chained .lazy.filter before .reduce in selectedSize.

🎯 Why: SwiftUI computed properties are evaluated very frequently during render cycles. Unnecessary intermediate array allocations (from eager filters) and full traversals (from reducing over size > 0) create avoidable memory and CPU overhead.

📊 Impact: Eliminates O(N) array memory allocations for selectedSize and hasSelection, and turns hasSelection from a full O(N) collection iteration into an O(1) best-case / early-exit operation.

🔬 Measurement: Run Time Profiler/Allocations instruments during UI updates (checking and unchecking checkboxes); view fewer [ScanResult] heap allocations and faster hasSelection getter resolution.


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

…t intermediate array allocations

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 work is now obsolete (duplicate) and stopping work on this task.

@acebytes acebytes deleted the bolt-performance-improvement-6607650057219304508 branch June 16, 2026 04:33
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