Martin von Zweigbergk 70073b94a8 repo: stop keeping a WorkingCopy instance ... The `Repo` doesn't do anything with the `WorkingCopy` except keeping a reference to it for its users to use. In fact, the entire lib crate doesn't do antyhing with the `WorkingCopy`. It therefore seems simpler to have the users of the crate manage the `WorkingCopy` instance. This patch does that by letting `Workspace` own it. By not keeping an instance in `Repo`, which is `Sync`, we can also drop the `Arc<Mutex<>>` wrapping. I left `Repo::working_copy()` for convenience for now, but now it creates a new instance every time. It's only used in tests. This further decoupling should help us add support for multiple working copies (#13).		2021-11-25 21:04:56 -08:00
..
test_bad_locking.rs
test_commit_builder.rs
test_commit_concurrent.rs
test_conflicts.rs
test_diff_summary.rs
test_git.rs	backend: make Vec inside CommitId non-public	2021-11-19 23:19:00 -08:00
test_index.rs	tests: avoid accessing working copy just to get its commit ID	2021-11-17 12:45:18 -08:00
test_init.rs	tests: avoid accessing working copy just to get its commit ID	2021-11-17 12:45:18 -08:00
test_load_repo.rs
test_merge_trees.rs
test_mut_repo.rs
test_operations.rs	tests: avoid accessing working copy just to get its commit ID	2021-11-17 12:45:18 -08:00
test_refs.rs
test_revset.rs	backend: make Vec inside CommitId non-public	2021-11-19 23:19:00 -08:00
test_revset_graph_iterator.rs
test_rewrite.rs
test_view.rs	tests: avoid accessing working copy just to get its commit ID	2021-11-17 12:45:18 -08:00
test_working_copy.rs	repo: stop keeping a WorkingCopy instance	2021-11-25 21:04:56 -08:00
test_working_copy_concurrent.rs	repo: stop keeping a WorkingCopy instance	2021-11-25 21:04:56 -08:00