create a worktree-tree without an intermediate index #4912
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.
Initially I didn't know where it would be beneficial to use
gitoxide
tree editing capabilities, but now foundcreate_wd_tree()
as candidate.Despite not exactly knowing why it's needed when applying a branch, it's easy for me to trigger it this way, while noting that it's also used
in many other places.
Baseline
735ms as baseline in the
GitLab
repository is quite respectable!After
Now it runs slightly faster at 549ms for a 33% speedup. However, the is likely going to be faster once it actually has to add objects, as these are now added in the main thread, while another thread is producing the status information.
Tasks
gix
Notes for the Reviewer
index.add_all()
. The 'control' part is particularly interesting as eventually, I'd really hope it's possible to avoid adding worktree files without user request.