perf: skip redundant shallow memo updates - #1186
Closed
MichaReiser wants to merge 1 commit into
Closed
Conversation
✅ Deploy Preview for salsa-rs canceled.
|
MichaReiser
force-pushed
the
perf-skip-shallow-update
branch
from
June 23, 2026 17:28
257a2db to
6990341
Compare
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
1 participant
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.
Make shallow memo updates explicit at call sites so only higher-durability verification performs memo writes. After the hot/cold-path split, release codegen already eliminates this work on current-revision cached hits, so this no longer has a measurable hot-path benefit.
Testing: Passed release-mode targeted validation and clippy.