Repository navigation
Reuse the validated Replay host update tree - #189
Merged
Merged
Conversation
This was referenced Nov 9, 2026
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.
Summary
Compatibility
The public API, Replay v1/v2 encoding and the layout/paint commit boundary stay the same. Each replacement still has a fresh tree identity and expires earlier handles. A host update now allocates one tree identity for its candidate.
Verification
For the refactoring baseline, one clean local Core Debug run on
45e651fused Visual Studio 2026 x64, 2 build workers and 4 test workers. Configure took 2.10 s, build 106.33 s, and CTest 30.25 s. The recent hosted source-only PR spent 299 s in the Core contracts step. These are baseline observations.