perf: eliminate redundant read_dispair calls in try_into_call

[thedavidmeister]

Summary

try_into_call previously called read_dispair three times — once inline and once inside each try_parse_rainlang call — totalling 12 sequential RPC round-trips just to read 4 immutable deployer addresses. At 300ms RTT (remote RPC) that is ~3.6s of avoidable latency.

Changes

• Add parse_bytecode_with_dispair: the parsing body extracted from try_parse_rainlang, takes a pre-fetched DISPaiR (no additional dispair reads).
• try_parse_rainlang is now a thin wrapper: read_dispair + parse_bytecode_with_dispair. All existing tests remain unchanged.
• try_into_call calls read_dispair once, clones for the first parse, moves for the second parse, and extracts interpreter/store upfront.

Result

RPC calls per generate_deposit_and_add_order_calldatas (dispair portion):

Before	After
12 (3× read_dispair)	4 (1× read_dispair)

Total for a single deposit+addOrder: 14 → 6 sequential eth_call round-trips, saving ~2.4s at 300ms RTT.

Test

Adds assertions to test_into_add_order_call verifying both config.evaluable.interpreter/store and tasks[0].evaluable.interpreter/store match the expected interpreter/store addresses (and match each other). This mutation-validates that both evaluables receive the correct dispair from the single shared read.

Closes #2776

Co-Authored-By: Claude noreply@anthropic.com

[coderabbitai]

Warning

Review limit reached

@thedavidmeister, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4080815a-60cf-469b-a838-48ec1ca5fd2a

📥 Commits

Reviewing files that changed from the base of the PR and between 8e382f8 and 85559f5.

📒 Files selected for processing (1)

• crates/common/src/add_order.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-06-29-issue-2776-dispair-cache

---

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