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.
As a prereq to #8, we need a way to iterate over an SST. This builds on top of the existing block iterator.
Since a
BlockIterator
holds a reference to aBlock
, it needs to live for at least as long as the block. When iterating over an entire SST, the easiest way to do this is to have theBlockIterator
own the block. I opted here to create aBlockLike
trait which is implemented for bothBlock
and&Block
. I suspect that once we start caching reads, we will want to pass around reference-countedBlock
values instead, but this approach lets us defer that discussion until later.