Skip to content

⚡ Bolt: Optimize computed properties to avoid intermediate array allocations#306

Closed
acebytes wants to merge 1 commit into
mainfrom
bolt-optimize-computed-properties-3461001768574288850
Closed

⚡ Bolt: Optimize computed properties to avoid intermediate array allocations#306
acebytes wants to merge 1 commit into
mainfrom
bolt-optimize-computed-properties-3461001768574288850

Conversation

@acebytes

Copy link
Copy Markdown
Contributor

💡 What: Replaced an eager filter followed by reduce with a .lazy.filter.reduce chain, and replaced !selectedResults.isEmpty with scanResults.contains(where:) in CacheoutViewModel. Added inline explanatory comments.
🎯 Why: In SwiftUI, computed properties on @Published view models can be evaluated frequently. Using an eager .filter array to check .isEmpty or reduce allocates intermediate arrays on every access, causing unnecessary memory churn.
📊 Impact: Eliminates O(N) array allocations for selectedSize and hasSelection, and turns hasSelection into an O(1) short-circuit operation when an item is selected.
🔬 Measurement: Profile with Instruments (Allocations track) while toggling selection to observe eliminated array allocations.


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

…cations

- Use `.lazy.filter` before `.reduce` in `selectedSize` to prevent O(N) intermediate array allocations.
- Replace `!selectedResults.isEmpty` with `scanResults.contains(where:)` in `hasSelection` to short-circuit evaluation.

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 a duplicate and stopping work on this task.

@acebytes acebytes deleted the bolt-optimize-computed-properties-3461001768574288850 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