use MemoryPool instead of allocator, fix examples #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MemoryPool is more performant and efficient than using a generic allocator, especially for lots of
create()s anddestroy()s of only a single type (Node(K, V, D)in this case)also refactored part of the BPlusTree struct for easier readability and nicer qualities like
BPlusTree(K, V, D).Nodeinstead of having detachedBPlusTree(K, V, D)andNode(K, V, D)(they are intrinsically linked)