refactor(storage): remove lifetime on iterators #1956
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.
What's changed and what's your intention?
Remove all the lifetime associated with iterators defined in Hummock.
This PR conflicts with PR #1928 on
use XXX
statements only at one location. It seems #1928 is ready and this PR will wait for it to be merged first.After this refactoring, we can bound the trait
StateStoreIter
by'static
. This will bypass the compiler limitation described in #1930 whenSend
is used to boundNextFuture
inStateStoreIter
.Refer to a related PR or issue link (optional)
#1930