[Move] Change transfer_and_freeze to freeze_object #672
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
lxfind
requested review from
awelc,
sblackshear,
gdanezis,
stella3d,
asonnino and
oxade
sblackshear
approved these changes
Mar 7, 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.
We used to have
transfer_and_freezein Move API where a recipient is specified. This no longer makes sense since an immutable object is shared and hence does not have an owner. There is no need to specify a recipient when freezing an object.This PR removes the recipient from the freeze API and rename it to
freeze_object.The event name and tests are also changed to reflect this.
The transfer to address API and transfer to object API are merged as a cleanup too.
Similar cleanups in test_scenario.rs.