Bring the published tree up to the source - #8
Merged
Conversation
The published snapshot dates from 2026-08-12; the source has moved on by about 3,350 lines across 10 files. The largest piece is the replacement policy work -- including finding the eviction victim from the cold end rather than scanning -- along with cache facades, the multilayer cache, storage engines, allocator and GC wiring, and a policy_bench example that was not published at all. The test module grows by roughly 1,000 lines with it, so the behaviour arrives with the tests that pin it rather than ahead of them. `cargo test` is green: 277 passed.
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
3 participants
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.
The published tree dates from 2026-08-12. The source has moved on by about 3,350 lines across 10 files, and this brings the published tree level with it.
The largest piece is the replacement policy work -- including finding the eviction victim from the cold end rather than scanning for it -- along with the cache facades, the multilayer cache, storage engines, allocator and GC wiring, and a
policy_benchexample that had never been published.The test module grows by roughly 1,000 lines with it, so the behaviour arrives together with the tests that pin it rather than ahead of them.
Verification
cargo testgreen: 277 passed, 0 failed.Unlike the MatrixRaft sync, nothing here was broken at the source -- this is a straight catch-up.