Martin von Zweigbergk b8f71a4b30 working_copy: in LockedWorkingCopy::drop(), discard unsaved changes ... In `LockedWorkingCopy::drop()`, we panic if the caller had not called `finish()`. IIRC, the idea was both to find bugs where we forgot to call `finish()` and to prevent continuing with a modified `WorkingCopy` instance. I don't think the former has been a problem in practice. It has been a problem in practice to call `discard()` to avoid the panic, though. To address that, we can make the `Drop` implementation discard the changes (forcing a reload of the state if the working copy is accessed again).		2023-09-01 12:25:47 -07:00
..
test_bad_locking.rs
test_commit_builder.rs
test_commit_concurrent.rs
test_conflicts.rs
test_default_revset_graph_iterator.rs
test_diff_summary.rs
test_git.rs
test_id_prefix.rs
test_index.rs
test_init.rs
test_load_repo.rs
test_merge_trees.rs
test_merged_tree.rs
test_mut_repo.rs
test_operations.rs
test_refs.rs
test_revset.rs
test_rewrite.rs
test_view.rs
test_working_copy.rs
test_working_copy_concurrent.rs
test_working_copy_sparse.rs
test_workspace.rs