Merged
Conversation
Also - removed the deprecated flexbuffer slice from example - fixed some cargo warnings
Contributor
|
What about |
Collaborator
Author
|
Btw, I also considered adding assertions instead of adding HEAD With Assertions |
Collaborator
Author
@krojew, oops, I should've noticed that |
krojew
reviewed
Apr 25, 2021
| /// Place an EndianScalar into the provided mutable byte slice. Performs | ||
| /// endian conversion, if necessary. | ||
| /// # Safety | ||
| /// Caller must ensure `s.len() > size_of::<T>()`. |
Contributor
There was a problem hiding this comment.
I think we should either list all safety requirements or none, e.g. no overlapping requirement is missing.
Collaborator
Author
There was a problem hiding this comment.
Done, I couldn't think of other requirements.
Contributor
|
Looks good! We should add resolution info to rust advisory after a release. |
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
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.
Also
PTAL @krojew
This should fix #5825
I didn't add any
// UNSAFE OKcomments since the existing code is considered safe due to previous testing