Key-value log passes correctness tests #23
Merged
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.
I feel fairly confident that the key value log is now implemented correctly, and would like to land this module into the
dev
andmaster
branches, ideally. I'll start with this PR fordev
.Some things still to figure out: The "right way" for the code to choose these constants
CHUNK_BITS
andCHUNK_BITC
. Ideally, we'd use associated constants of a (currently non-existent) type parameter, to impose zero runtime overhead for storing these constants in the data structure itself.