//! The in-memory-only datastore implementation. This is the simplest and
//! generally fastest implementation, but it has these drawbacks:
//!
//! * Data is not persisted.
//! * Transaction changes cannot be rolled back on error.
//! * Locking is coarse-grained; only one thread can write to the datastore at
//! a time. Consequently, this may actually perform worse on highly
//! concurrent write-heavy workloads.
pub use ;
full_bench_impl!;
full_test_impl!;