Conversation
A SoilIndexedCollection holds any number of SoilObjectIndexes. Each of them derives its key from the added object by sending it one selector, so the same object can be looked up by different properties. Until the creating transaction commits, the backend index of a SoilObjectIndex has no file yet. SoilMemoryIndexStore keeps its pages in memory for that phase; the journal entry written during serialization creates the file on commit, and materialization reconnects to the index in the segment. Take the ideas from the spike in #961 but not its scaffolding: SoilIndex keeps the file store as its default and gains #beMemoryStore to opt into memory pages explicitly, instead of defaulting to memory and repairing that in #path:.
Index keys made from strings of different length do not sort alphabetically:
String>>asIndexKeyOfSize: packs the bytes into an integer, so a longer string
always sorts after a shorter one ('b' is 98, 'aa' is 24929). The order the
values of an index come back in therefore says nothing about which key they
were stored under, which is what the test wanted to show.
noha
force-pushed
the
spike-indexed-collection-rebased
branch
from
September 6, 2026 22:26
1602092 to
d046ec1
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.
No description provided.