⚡ Bolt: [Fast Dense Integer Set Tracking] Replaced Set<number> with Uint8Array for visited indices

[AhmmedSamier]

💡 What: Replaced per-query Set<number> allocations in SearchEngine.performUnifiedSearch with a pre-allocated Uint8Array buffer (visitedIndicesBuffer) and a fast O(K) reset tracker (visitedIndicesTracker) wrapped in a try/finally block.

🎯 Why: During burst searches, instantiating new Set<number>() and performing hash-based lookups causes significant garbage collection overhead and CPU cycles in the hot path. A pre-allocated Uint8Array provides unboxed, direct memory access for true O(1) membership checks without allocating new objects.

📊 Impact: Reduces worst-case burst search latency (e.g., when filtering large numbers of scoped items with no matches) by ~40% (from ~36ms to ~21ms).

🔬 Measurement: Verified using bun run benchmarks/search_burst.bench.ts.

---

PR created automatically by Jules for task 17235746280556656312 started by @AhmmedSamier

[google-labs-jules]

👋 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.

[coderabbitai]

Warning

Rate limit exceeded

@AhmmedSamier has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 37 minutes and 31 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 470c6ecc-8cd4-412e-84b6-aa557f2104bf

📥 Commits

Reviewing files that changed from the base of the PR and between 95aac54 and 3469777.

📒 Files selected for processing (3)

• .jules/bolt.md
• language-server/benchmarks/results_burst.json
• language-server/src/core/search-engine.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt-fast-dense-integer-set-tracking-17235746280556656312

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 37 minutes and 31 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}