That makes a lot of sense. I should have thought about that!

I really dig the idea of `git_iterator_next` as a simple wrapper. If you can add that, and `GIT_ITEROVER` as a return value, we'd end up with a very nice iterator API for the filesystem while keeping the original workdir/tree iterators intact.