lib/runtime: implement ext_kill_child_storage and ext_get_allocated_child_storage #1110
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
noot
reviewed
Sep 29, 2020
| @@ -23,7 +23,7 @@ import ( | |||
| ) | |||
|
|
|||
| // ChildStorageKeyPrefix is the prefix for all child storage keys | |||
| var ChildStorageKeyPrefix = []byte(":child_storage:") | |||
| var ChildStorageKeyPrefix = []byte(":child_storage:default:") | |||
There was a problem hiding this comment.
In the spec, F.1.9 it says this key must be prefixed with :child_storage:default:
This was referenced Oct 19, 2022
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.
Changes
ext_kill_child_storageas defined in spec F.1.14ext_get_allocated_child_storageas defined in spec F.1,12:child_storage:default:as defined in spec F.1.9Tests
Checklist
Issues