-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Frame remove_all with size limit.
#9106
Conversation
The solution is simply to add |
Yes, updating is very straight forward. Seems better to me than having two function for the same thing. |
athei
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API changes look good to me. But we need to remove some duplication.
|
bot merge |
|
Trying merge. |
|
maybe it worth documenting that the function remove_all, and warn that it removes all overlay, and up to limit in the backend, people shouldn't rely on the fact that it removes exactly up to the limit. |
* remove prefixed content with limit. * test match * factor comment and factor ext limit removal. * fix benchmark Co-authored-by: Shawn Tabrizi <[email protected]>
Fixes #9002.
Note that it breaks existing frame api (could have define new function with the limit but it does not seem good).
Affected APIs:
remove_prefixclear_prefixkill_prefixremove_allTo fix these APIs to act the same as before, simply add an additional input parameter of
None.Also rename:
KillChildStorageResult->KillStorageResultpolkadot companion: paritytech/polkadot#3257