imag/lib/core/libimagstore at 3c801a264d6b3ef2ef77a16c759ef918d66a9357 - matthiasbeyer/imag

History

Matthias Beyer cc11162dd4 Fix: In-Memory filesystem backend did not remove on rename The implementation of the in-memory filesystem for testing imag code did not actually use `HashMap::remove()` when an entry was moved, but `HashMap::get().cloned()`, which caused the original entry to exist _after_ the move. I'm not sure why this did not fail much earlier, but it was clearly wrong. This commit adjust the test to check the "filesystem" before checking the store and fixes the bug. Signed-off-by: Matthias Beyer <mail@beyermatthias.de>		2018-10-09 17:37:56 +02:00
..
src	Fix: In-Memory filesystem backend did not remove on rename	2018-10-09 17:37:56 +02:00
.gitignore	Reorganize code in subdirs	2017-08-27 15:12:09 +02:00
Cargo.toml	Update dependencies	2018-10-06 12:21:20 +02:00
README.md	Fix broken README symlinks	2017-08-27 15:13:25 +02:00

libimagstore

The store is the heart of everything. Here lives the data, the complexity and the performance bottleneck.

The store offeres read/write access to all entries.

The store itself does not offer functionality, but has a commandline interface "imag-store" which can do basic things with the store.