-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
lang: Zero copy deserialization #202
Merged
Merged
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
This was referenced Apr 17, 2021
Closed
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.
Addresses
Provides the ability to opt into zero copy deserialization for accounts. This means, instead of using borsh, accounts are defined with "plain old data" types that map 1-1 to the bytes in the backing
AccountInfo
's&mut [u8]
.Other than being more efficient, the most salient benefit this provides is the ability to define account types larger than the max stack or heap size. This is used in special cases, for example, the Serum DEX event queue. When using borsh, one is limited, since the account has to be copied and deserialized into a new data structure. With zero copy deserialization, everything is, effectively, lazy loaded on field access.
To use this feature, one must define their account as
Or for associated accounts
Otherwise, Borsh is still used, by default. The
ts
client will still work as expected in either case.