[Object Ownership #2] Add trasfer_to_object API in Transfer.move #293
Conversation
lxfind
requested review from
huitseeker,
awelc,
patrickkuo,
sblackshear,
gdanezis and
oxade
|
This is interesting. I was not aware objects could own other objects. |
|
@lxfind @sblackshear |
|
Yeah there will be some work needed in the client to support this, but don't worry about it at the moment. |
Based on the current design, yes. If X owns Y, and we freeze X, Y is also frozen (all objects owned by X will be frozen). |
lxfind
changed the title
| public native fun transfer_to_id<T: key>(obj: T, id: IDBytes);*/ | ||
| /// Transfer ownership of `obj` to another object `owner`. | ||
| // TODO: Add option to freeze after transfer. | ||
| public fun transfer_to_object<T: key, R: key>(obj: T, owner: &mut R) { |
There was a problem hiding this comment.
We might want to make this a friend function if we're only planning to expose it in certain collection published in genesis. But let's see how it shakes out.
| } | ||
|
|
||
| /// Transfer ownership of `obj` to another object with `id`. | ||
| native fun transfer_to_object_id<T: key>(obj: T, id: IDBytes); |
There was a problem hiding this comment.
Just a caution--if you try to test this, I think it will crash due to #309.
lxfind
force-pushed
the
add-authenticator
branch
from
7f779f7 to
b8f6ea7
Compare
lxfind
force-pushed
the
allow-transfer-to-object
branch
from
d44066e to
9501a69
Compare
lxfind
force-pushed
the
allow-transfer-to-object
branch
from
9501a69 to
35fa4d3
Compare
This is the second step towards #99.
It allows us to transfer an object to another object in Move.
To do so we added a
transfer_to_objectAPI in the Transfer module, which then invokes a native function to emit the corresponding event.Latter in the adapter we process the event and change the owner accordingly.