refactor(ui): Use an iterator instead of Vec
to represent events
#4361
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.
(Extracted from #3512)
This patch changes
TimelineStateTransaction::add_remote_events_at
to take anIntoIterator<Item = Into<SyncTimelineEvent>>
forevents
. In the current code, it saves oneiter().map(Into::into).collect::<Vec<_>>()
, but it will save another one when we will supportVectorDiff
s coming from theEventCache
.It also avoids to allocate a vector to pass new events (this mostly happens in the tests, but it can happen in real life).
EventCache
storage #3280