Backend: remove unnecessary draining of changes to be applied #80
Conversation
This file contains 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
gterzian
commented
Apr 1, 2021
| actor: Option<(amp::ActorId, u64)>, | ||
| ) -> Result<amp::Patch, AutomergeError> { | ||
| let mut pending_diffs = HashMap::new(); | ||
|
|
||
| for change in changes.drain(..) { | ||
| for change in changes.into_iter() { |
There was a problem hiding this comment.
Here using drain would have made a lot of sense if you had a mutable reference to the vector, and that after the changes had been applied, you expected the caller to still use the now empty one.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A few nits, caught my attention when looking at #78