Use dyn where possible, including dyn based progress traits
#1008
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.
Implement a proper worktree reset, eventually leading to a high-level reset similar to how git supports it.
Facilitate compile time reduction
ProdashProgresscan also useCountordyn Count, ordyn Progressgix-packdata-io off using feature togglesgixfeature toggles: remote-connection, blob-diff, describe, attributes->worktree-checkout, attribute->pathspecs->submodules, mailmap../../../. Further, assure that we don't write such refs when receiving them from the server.Tasks
checkout()method as technically that's areset --hardwith optional overwrite check. Could it be rolled into one, with pathspec support added?Postponed
What follows is important for resets, but won't be needed for
cargoworktree resets.Research
mergeandkeep? How to controlrefresh?git resetandgit checkoutin terms ofHEADmodifications. With the former changingHEADs referent, and the latter changingHEADitself.