mem: fix incorrect offset in Write #263
Merged
Conversation
This file contains 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
Signed-off-by: Yerden Zhumabekov <yerden.zhumabekov@gmail.com>
Signed-off-by: Yerden Zhumabekov <yerden.zhumabekov@gmail.com>
Signed-off-by: Yerden Zhumabekov <yerden.zhumabekov@gmail.com>
|
|
0xmichalis
approved these changes
Sep 2, 2020
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.
Hello, everyone,
Recently I needed an in-memory implementation of io.WriteSeeker and tried to use File. Unfortunately, my code panicked using afero's File implementation whereas os.File implementation worked flawlessly.
It looks like Write incorrectly sets offset after appending data. I've written a test for correct behaviour and implemented a fix.
Also, I check
whencevalue in Seek againstio.Seek*literals so it reads easier for people with bad memory like me.