Extract spacetimedb-memory-usage
& Nix bindings
dep on spacetimedb-data-structures
#2919
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.
Description of Changes
The trait
MemoryUsage
is moved to its own crate (spacetimedb-memory-usage
) to facilitate extracting outPool<T>
fromPagePool
as done in the next PR #2920. Having more small crates is a great thing. This is also done to get rid of some dependencies ofspacetimedb
(crates/bindings
).Preparatory work extracted from #2911.
API and ABI breaking changes
None
Expected complexity level and risk
2, this is mostly just code motion.
Testing
Covered by existing tests.