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

Deferred serialization / deserialization holes #44

Open
mgsloan opened this issue May 31, 2016 · 0 comments
Open

Deferred serialization / deserialization holes #44

mgsloan opened this issue May 31, 2016 · 0 comments

Comments

@mgsloan
Copy link
Owner

mgsloan commented May 31, 2016

packer has a really cool idea where during serialization you can create known-sized holes, and later fill them. I haven't really considered the details, but it would be cool to generalize this to deserialization as well. A hole in deserialization would essentially be explicit decoding laziness. It'd probably use a data frame much like the streaming support.

Another thought on this is that for serialization it'd be good to be able to run some assertion function to check that all the holes have been filled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant