Repository navigation
Avoid serializing if lockfile does not change - #4945
Merged
Merged
Conversation
charliermarsh
approved these changes
Jul 9, 2024
ibraheemdev
force-pushed
the
ibraheem/fast-lock
branch
from
July 9, 2024 20:58
49f4bc8 to
8ce42a3
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Avoid serializing and writing the lockfile if a cheap comparison shows that the contents have not changed.
Test Plan
Shaves ~10ms off of #4860 for me.