Benchmark burn_nft call with deep nesting #240
Merged
Conversation
This file contains hidden or 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
Maar-io
suggested changes
Nov 6, 2022
Contributor
Maar-io
left a comment
Maar-io
left a comment
There was a problem hiding this comment.
since lookup_root_owner is recursive call and can be repeated n times, any function calling it should calculate weight according to this n.
Take a look for example at the set_priority()
Maar-io
reviewed
Nov 9, 2022
ilionic
changed the title
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.
Part of #241
mint_and_send_to_parentfunction which mintsnitems and sends to parent to create deep nested chain of nfts.burn_nftandreject_nft( since it's using burn ) withn