⚡ Bolt: [performance improvement] Avoid String allocation in Segment …

[SayanthRock]

User description

…parsing

---

CodeAnt-AI Description

Reduce memory use while parsing RockQL transformations

What Changed

• RockQL segment parsing now reuses slices of the original query text instead of creating a separate string for each segment
• Parsing behavior, transformation handling, and diagnostic locations remain unchanged

Impact

✅ Lower memory use during query parsing
✅ Fewer allocations for multi-segment queries

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

Summary by CodeRabbit

• Performance Improvements
  • Reduced memory allocations during segment parsing by reusing text directly from the source input.
  • Preserved existing parsing and transformation behavior while improving efficiency.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	45cef4c	Aug 13, 2026 · 02:20	02:22

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

---

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

[Copilot]

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 47da01ab-01ce-495c-9d93-699503cfe9e9

📥 Commits

Reviewing files that changed from the base of the PR and between 7339397 and 45cef4c.

📒 Files selected for processing (2)

• .jules/bolt.md
• compiler/rockql-parser/src/lib.rs

---

📝 Walkthrough

Walkthrough

The parser now borrows segment text from the input source. Segment splitting, storage, and transformation dispatch use borrowed slices without intermediate owned String allocations. A learning entry documents this implementation guidance.

Changes

Borrowed segment parsing

Layer / File(s)	Summary
Segment lifetimes and parsing flow compiler/rockql-parser/src/lib.rs, .jules/bolt.md	Segment, split_segments, and push_segment now use borrowed source slices. Transformation parsing receives borrowed text directly. The learning entry records the same guidance.

Estimated code review effort: 2 (Simple) | ~10 minutes

Mergeability Score: ⚪ Minimal · up to 45cef

This is a small, localized parser performance change, and no actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

• Sayanthrock-Developer/ROCKQL#5: Both PRs update Segment and split_segments to borrow input slices instead of allocating String values.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: avoiding String allocation during Segment parsing.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt-optimize-segment-parsing-7417451691428726344

---

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