Skip to content

fix: make array mutator methods mutate the receiver in place#55

Open
jtippett wants to merge 1 commit into
TheUncharted:masterfrom
jtippett:fix/array-mutation
Open

fix: make array mutator methods mutate the receiver in place#55
jtippett wants to merge 1 commit into
TheUncharted:masterfrom
jtippett:fix/array-mutation

Conversation

@jtippett

@jtippett jtippett commented Jul 9, 2026

Copy link
Copy Markdown

Summary

push, pop, shift, unshift, splice, reverse, and fill computed their return value against a clone and never mutated the receiver — arr.push(x) didn't persist. Another silent-wrong-answer case on a documented-supported surface (array methods).

Changes

  • Mutator methods mutate in place and write back to the receiver variable, consistent with the value-typed SetIndex/SetProperty store-back pattern described in AGENTS.md.
  • Regression tests in tests/objects_arrays.rs.

Test plan

  • Unit tests pass (cargo test)
  • make lint clean
  • CI passes

Related issues

None open. We run this patch in production via ex_zapcode.

push, pop, shift, unshift, splice, reverse, and fill computed their
return value against a clone and never wrote back, so arr.push(x) did
not persist. They now mutate in place and write the result back to the
receiver variable.
@jtippett
jtippett requested a review from TheUncharted as a code owner July 9, 2026 09:29
@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 59 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: 3055a16a-1eb7-406d-a625-250c0809d47f

📥 Commits

Reviewing files that changed from the base of the PR and between ebc06fd and 9159f2a.

📒 Files selected for processing (3)
  • crates/zapcode-core/src/vm/builtins.rs
  • crates/zapcode-core/src/vm/mod.rs
  • crates/zapcode-core/tests/objects_arrays.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

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