Move memtable freeze question to Week 1 Day 6 - #234
Merged
Merged
Conversation
Place the freeze interleaving question after learners have implemented the full Week 1 write path. Name the state read-lock boundary and the cached-Arc failure case. AI-Assisted: GPT-6 Sol + Sentinel
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.
Summary
Move the stale-snapshot memtable question from Week 1 Day 1 to Day 6. The Day 6 version asks learners to inspect the state read-lock scope in
putand reason about the cached-Arcfailure case after they have completed the Week 1 write path.This is a book-only, two-line change: one question removed and one question added. No code, starter, test, or navigation file changes.
Validation
a0a3418b28315949ebb1658a70ab83fd44c53484.AI-Assisted: GPT-6 Sol + Sentinel