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
..
benches
gen-protos	Use { workspace = true } to appease VS Code's Cargo.toml parser	2023-08-22 21:38:53 -07:00
src	working_copy: in LockedWorkingCopy::drop(), discard unsaved changes	2023-09-01 12:25:47 -07:00
tests	working_copy: in LockedWorkingCopy::drop(), discard unsaved changes	2023-09-01 12:25:47 -07:00
testutils	tests: leverage create_tree() in a few more tests	2023-08-30 19:58:42 -07:00
Cargo.toml	merged_tree: add diff iterator	2023-08-25 06:40:36 -07:00