Fix misuse of Integer.SIZE in FileWriteOutBytes.writeInt #9723
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.
Description
In the
FileWriteOutBytes#writeInt(int)
method, the argument passed toflushIfNeeded()
isInteger.SIZE
while theInteger.BYTES
should be used.Problem
This bug will incur one extra file write operation in some cases. For example, if we would like to write 4 KB of ints using
FileWriteOutBytes#writeInt(int)
, theflush()
method will be called twice. After fixing this bug, theflush()
method will be called only one.This PR has:
Key changed/added classes in this PR
FileWriteOutBytes
FileWriteOutBytesTest