-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Leave overflow logic to go-msgio #1910
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
I think this was meant to deal with the case where
buf
is smaller thanr.buf
but I think it should readbuf = buf[:copied]
(all the bytes up tocopied
, not all the bytes after).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.
no i believe this is right as is -- (this seems to be way more complicated than it should be, though).
buf
here is the user passed inbuf
which will receive the datar.drainBuf(buf)
will copy intobuf
all the stuff inr.buf
that fits intobuf
.r.buf
to ber.buf[n:]
(i.e. already copiedbuf[0:n]
intobuf
)copied
is the number of bytes copied intobuf
. this may be a number smaller thanlen(buf)
, and if so, we want to setbuf
to bebuf[copied:]
so that further copies into buf only fill up the remaining (unused) bytes.buf
, and in that case we only write into the originalbuf[copied:]
, because that's what hasn't been written to.all of this is useless anyway because exit if
copied > 0
, which seems to have been added later, as a short circuit for simplicity.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.
also, wow this code. @jbenet needs to write cleaner crap.
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.
Ah, thanks for the explanation. This is me being a go newbie, despite being an experience C programmer. I was thinking that somehow
buf
was manipulating a reference andbuf = buf[copied:]
was changing the result that the caller sees.