Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Make VM parametric in serialization format #28

Open
sblackshear opened this issue Jan 28, 2022 · 2 comments
Open

[Feature Request] Make VM parametric in serialization format #28

sblackshear opened this issue Jan 28, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@sblackshear
Copy link
Contributor

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.

@sblackshear sblackshear added the enhancement New feature or request label Jan 28, 2022
@tnowacki
Copy link
Contributor

tnowacki commented Feb 1, 2022

This will be rather tricky, but not impossible, since there are BCS-encoded values inside of compiled module+script bytes, in the form of constants

@sblackshear
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants