WIP: Storage refactor #143
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reworks and extends the Fadroma storage functionality by introducing a flexible storage key building system and storage types built on top of that. All keys are built using a single allocation. The storage types allow a single declaration, similar to the CW Plus types, but due to the key system we allow for customizing how the type is stored and also the types from which the keys are created can now be expressed in code now which introduces the concept of strongly-typed keys. For example, if we store data under an address + an index we can now express that as
TypedKey2<CanonicalAddr, u64>. In addition, the existingCanonize/Humanizetraits allow us to extend the new storage types to accept types that canonize to the given typeTand inversely, load and humanize the typeTto the given type requested. This means we can canonize and store in a single call (and load and humanize).