erase old version abi before insert new version abi when set abi#70
Open
gzliudan wants to merge 1 commit intoEOSIO:masterfrom
Open
erase old version abi before insert new version abi when set abi#70gzliudan wants to merge 1 commit intoEOSIO:masterfrom
gzliudan wants to merge 1 commit intoEOSIO:masterfrom
Conversation
…t insert new element when there's same key already in it
heifner
reviewed
Sep 15, 2020
heifner
reviewed
Sep 15, 2020
| context->contracts.insert({name{contract}, std::move(c)}); | ||
| const name key {contract}; | ||
| context->contracts.erase(key); | ||
| context->contracts.insert({key, std::move(c)}); |
Contributor
There was a problem hiding this comment.
Should be able to use: context->contracts.insert_or_assign(name{contract}, std::move(c));
Author
There was a problem hiding this comment.
Yes, insert_or_assign is better.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Because element keys in a map are unique, the insertion operation checks whether each inserted element has a key equivalent to the one of an element already in the container, and if so, the element is not inserted. So when we set a contract of new version, we must erase old version first. Otherwise the new contract is not inserted, and the old contract is still in context.