⚡ Bolt: [performance improvement] Replace char_indices with optimized scanning

[SayanthRock]

User description

💡 What: Optimized two bottleneck areas in the RockQL parser (split_segments and parse_transform) by replacing .char_indices() with .match_indices('|') and .find(char::is_whitespace).

🎯 Why: The original implementation used .char_indices() to scan strings character-by-character. This adds unnecessary overhead because it mandates full UTF-8 decoding for every single character. Searching for a single byte (|) can bypass decoding entirely by using match_indices, and finding whitespace can be offloaded to .find() which internally applies optimizations while preserving Unicode semantics perfectly.

📊 Impact: Reduces CPU cycles spent on text decoding during the query parsing phase, notably on large scripts or heavily chained transformations.

🔬 Measurement: Run standard query benchmarks. The speed-up will primarily scale with input script length. The optimizations have been verified with cargo test to ensure exact functionality preservation (especially Unicode semantics).

---

PR created automatically by Jules for task 8584763610092353124 started by @SayanthRock

---

CodeAnt-AI Description

Speed up RockQL query parsing without changing parsing behavior

What Changed

• Query segments split by | are scanned more efficiently
• Transform keywords are located faster while still recognizing Unicode whitespace correctly
• Existing segment boundaries, positions, and Unicode parsing behavior are preserved

Impact

✅ Faster parsing for large RockQL scripts
✅ Lower CPU use during chained transformations
✅ Unicode whitespace remains supported

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

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

[ai-coding-guardrails]

You've hit your review limit for the week, but don't worry you'll get some more next week!

Contact us at hello@zenable.io if you want this rate limit to go away

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	9b7ceb2	Aug 14, 2026 · 22:15	22:16

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Important

Review available on request

• 🔍 Trigger review

Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment @coderabbitai review to review the latest changes. For a full review, comment @coderabbitai full review.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1c373c31-96d7-422e-ba51-7015546f55bf

---

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

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