Currently we test the concurrency of adding an element (either popping off the free list or in a new index), and cleaning the deletion queue to add them to the free list. These things are fine, but we should test concurrent deletion (in case elements get tacked on to the queue multiple times) and concurrent updates (ensuring that we don't have corrupt data at any time).
We'll also want type specific tests.
Also, to implement the concurrent update tests, it may make sense to make it possible to "subscribe" to change notifications for a given key.
Currently we test the concurrency of adding an element (either popping off the free list or in a new index), and cleaning the deletion queue to add them to the free list. These things are fine, but we should test concurrent deletion (in case elements get tacked on to the queue multiple times) and concurrent updates (ensuring that we don't have corrupt data at any time).
We'll also want type specific tests.
Also, to implement the concurrent update tests, it may make sense to make it possible to "subscribe" to change notifications for a given key.