Asynchronous blaming

[figsoda]

Currently, in a large git repository, it takes a long time (~30s for https://github.com/nixos/nixpkgs) to start up git-dive. It would be nice if it starts immediately with just the plain file and gradually fills in blame information over the 30s.

[epage]

Yeah, git2 is quite a bit slower than git for blaming.

Loading asynchronously is a good idea! It won't quiet work in one-shot mode but this should work well for TUI mode. I've put tag this to be part of the TUI work.

[Byron]

gitoxide has all the functionality that's needed to do blaming (i.e. full rename and copy tracking, diffing/hunk generation), but lacks a convenient API. When that changes, using it would definitely speed up the synchronous mode while enabling efficient multi-threading.

[epage]

Yeah, I either might prototype blame support on top of gitoxide or contribute it. Another major feature I want is reverse blame support (#21) and git2 doesn't support that either.

[Byron]

It looks like git dive is envisioned to become the blame tool I always wanted. Once there is a timeline ideally with the ability to track a particular set of consecutive lines a dream will come true. Or if its too specific, a way to understand how a particular hunk of code came to be over time.