You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VM uses BCS for serialization, but there's nothing fundamental preventing Move from supporting multiple serialization formats. Allowing the adapter to choose a serialization format for the VM would enable more efficient usage of Move in settings where the host system's data is not BCS-encoded.
The text was updated successfully, but these errors were encountered:
Ah, interesting point... I think that is ok, though. It means the VM will always have to understand how to deserialize BCS bytes into a MoveValue to execute code, but at least we can free clients from needing to pass BCS into the VM and reading BCS output if they would prefer to use a different format.
The VM uses BCS for serialization, but there's nothing fundamental preventing Move from supporting multiple serialization formats. Allowing the adapter to choose a serialization format for the VM would enable more efficient usage of Move in settings where the host system's data is not BCS-encoded.
The text was updated successfully, but these errors were encountered: