Martin von Zweigbergk 30939ca686 view: return &HashSet instead of Iterator ... We want to be able to be able to do fast `.contains()` checks on the result, so `Iterator` was a bad type. We probably should hide the exact type (currently `HashSet` for both readonly and mutable views), but we can do that later. I actually thought I'd want to use `.contains()` for indiciting public-phase commits in the log output, but of course want to also indicate ancestors as public. This still seem like a step (mostly) in the right direction.		2021-01-16 13:00:05 -08:00
..
test_bad_locking.rs	view: return &HashSet instead of Iterator	2021-01-16 13:00:05 -08:00
test_commit_builder.rs
test_commit_concurrent.rs	view: return &HashSet instead of Iterator	2021-01-16 13:00:05 -08:00
test_diff_summary.rs
test_evolution.rs
test_git.rs	view: return &HashSet instead of Iterator	2021-01-16 13:00:05 -08:00
test_index.rs
test_init.rs
test_load_repo.rs
test_merge_trees.rs
test_operations.rs	view: return &HashSet instead of Iterator	2021-01-16 13:00:05 -08:00
test_transaction.rs	view: return &HashSet instead of Iterator	2021-01-16 13:00:05 -08:00
test_view.rs	view: return &HashSet instead of Iterator	2021-01-16 13:00:05 -08:00
test_working_copy.rs
test_working_copy_concurrent.rs