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

Zero copy serialization for parts of smart contracts #50

Open
abizjak opened this issue Jul 12, 2021 · 0 comments
Open

Zero copy serialization for parts of smart contracts #50

abizjak opened this issue Jul 12, 2021 · 0 comments
Labels
[Type] Task An additional feature or improvement.

Comments

@abizjak
Copy link
Contributor

abizjak commented Jul 12, 2021

Some types and values (e.g., account addresses) are likely to benefit from a more efficient serialization scheme, both in code space and execution time.

This will also allow removing the reliance on alloc.

We should consider having a more precise interface to serialization that is harder to use, but allows for zero-copy deserialization for parts where it matters.

Improvements should be accompanied by data and benchmarks.

@abizjak abizjak added the [Type] Task An additional feature or improvement. label Jul 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Task An additional feature or improvement.
Projects
None yet
Development

No branches or pull requests

1 participant