Module dochy_fs::history[−][src]

History’s filenames have a tag(arbitrary string given by user) control number(increases when start_new is called) order( numbers ancestors of this history file have. if order is (1,2,1,1) ancestors have orders (1)<- grand grandparent (1,2)<- grand parent (1,2,1)<- parent )

get_peekable_info

You can peek the file to be derived in the next save, but the Mutex is needed for save and load. If you call save or load while the MutexGuard is alive, deadlock occurs.

init_dochy_cache_us ^⚠

The backdoor to change DochySrc while running. References of PeekableCacheInfo for the history_dir will corrupt If save / load in the history_dir is running, calling this results undefined behavior

list_histories

load_history_file

Loads a history file.

load_history_file_data

save_history_file

calculates the diff from the latest save file(most of the time) and save the diff file.

save_history_file_nb

calculates the diff from the latest save file(most of the time) and save the diff file. This is non-blocking. RootObject is cloned and saved. RootObject consists of some Arcs so the cloning costs nearly zero. This system employs Copy on Write strategy. Actual copy occurs when the memory managed by Arc is modified before the saving is finished using Arc::make_mut.

save_history_file_nb_if_vacant

Saves when no save-thread is runnning for the history_dir. Calling this function concurrently for the same history_dir can make the evaluation incorrect.

set_current_root_obj_info

During save and load, the RootObject’s ID and the selected file is recorded. If you use the same RootObject in the next save, the file to be derived is automatically selected by the system.

Module dochy_fs::history[−][src]

Structs

Functions