Open
Conversation
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
1 participant
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.
Ran into this when trying to put together a zero-copy encoder for RESP - you really kinda have to use a noncontiguous implementation of Buf for that to work with protosocket.
The issue is that if a buffer was backed by noncontiguous slices,
.chunk()will usually only return the first section.So we'll only partially write that buffer out to the wire before moving onto the next, and then when we come back to do our
advancebookkeeping, we get totally off-track.I'm not really entirely sure this properly handles things either... but it's at least closer for well-behaving implementors of
chunks_vectored, I think?