This repository was archived by the owner on Nov 6, 2024. It is now read-only.
Serialization doc #11
Closed
Conversation
This file contains hidden or 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
Signed-off-by: Alexandra Iordache <[email protected]>
alxiord
requested review from
alexandruag,
jiangliu,
sameo and
andreeaflorescu
jiangliu
reviewed
Dec 30, 2019
| ### Portability | ||
|
|
||
| The bindings' byte representation is arch-dependent, rendering both RFCs | ||
| submitted so far un-portable. |
There was a problem hiding this comment.
Do we plan to support cross platform portability?
|
Closing in favor of #14, please direct all feedback, if any, there. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As discussed in the rust-vmm syncup on 2019-11-14, I'm adding a doc to iterate on wrt serialization support, in order to pin down the various requirements and restrictions from all the consumers of this crate.
After reaching a conclusion on this doc, we can move forward with an implementation that fits at least all the use cases that we're presently aware of.