Conversation
Owner
Author
|
Everything ready!!!!! |
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.
Field<String>covering padding, exact fit, overflow, and UTF-8 multibyte handling in section names (seetests/general.rs).Field<number>updates verifying successful writes andFileParseError::ValueTooLargeerrors.Field<number>::updatenow returnsResultand errors withFileParseError::ValueTooLargeif the value does not fit.Field<String>::updatenow accepts&strinstead of&String, reducing unnecessary allocations when updating string fields.Field<String>::updateto ensure that when the new value is shorter than the field size, any leftover bytes are properly zeroed out, and UTF-8 multibyte strings are handled correctly. In previous versions, some bytes from the old value could remain in the binary.Field<number>::updateto propagateFileParseError::ValueTooLargeerrors.write_filemethod for ELF format, providing a consistent read/write interface across all formats.endiannessfrom header and parse program and section headers with the appropriate byte order. A new valueelf::header::endiannessnow exists.endiannessis handled correctly.write_filemethod for Mach-O format, providing a consistent read/write interface across all formats.macho::header::endiannessnow exists.