-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add rkyv serialization #208
Conversation
I omitted writing fuzzing tests. We would only test if rkyv can (de)serialize |
} | ||
|
||
#[cfg(test)] | ||
#[cfg_attr(miri, ignore)] // https://github.com/rust-lang/unsafe-code-guidelines/issues/134 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this stacked borrows violation come from our code, or rkyv's?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rkyv. rust-lang/unsafe-code-guidelines#134 (comment)
Actually, I think I see what the problem is in their code. In repr.rs:40-62 they would need to replace self.inline.bytes.as_ptr()
with self.inline.bytes[..].as_ptr()
to make MIRI understand what is going on. If I don't forget it, I'll try if that fixes the problem.
Not adding to the fuzzing framework is fine with me, we don't have fuzz coverage for |
Thanks for the PR! I haven't used |
@Kijewski sorry for the quick succession of comments here. Just realized we don't have any tests for |
No description provided.