-
Notifications
You must be signed in to change notification settings - Fork 76
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
Improve IntoBytes
padding analysis
#1112
Comments
In theory, the impl of Note that even the problem of detecting whether or not a type is unsized is hard - there's no syntactic way to determine whether a concrete type is unsized. |
Many dynamically sized types can be
derive(FromBytes)
but notderive(IntoBytes)
because of shortcomings in our padding analysis. For example:Presently, a user must either mark
Example
asrepr(C, packed)
, or they must modelExample
instead as a composite struct containingRef
s to theHeader
and[Body]
.Can we make our analysis more sophisticated in this case?
The text was updated successfully, but these errors were encountered: