Bound auto-reload render memory for distant edits - #15848
Draft
warp-agent-staging[bot] wants to merge 1 commit into
Draft
Bound auto-reload render memory for distant edits#15848warp-agent-staging[bot] wants to merge 1 commit into
warp-agent-staging[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
This PR was generated with Warp. Comment   |
warp-agent-staging
Bot
added
factory:wilson
area:performance:memory
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Bound auto-reload render memory by keeping one logical content edit while queuing ordered, per-hunk render deltas for distant edits. Edits with overlapping render ranges retain the existing combined fallback.
Linked Issue
APP-5834
Testing
cargo nextest run -p warp_editor(502 passed)cargo clippy -p warp_editor --all-targets --tests -- -D warnings./script/format --checkFull
warpcompilation reached the app crate but was killed by the sandbox memory limit; CI will provide app-level coverage.I have manually tested my changes locally with
./script/runAgent Mode
CHANGELOG-NONE