[PR 3/5] Implement Unsafe API to iterate over segments and access its data #336
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
fzhinkin
changed the title
fzhinkin
force-pushed
the
bulk-api-part-1
branch
from
d105268 to
edd4461
Compare
fzhinkin
force-pushed
the
bulk-api-part-2
branch
from
0a8eff3 to
94e8786
Compare
shanshin
approved these changes
Jun 21, 2024
fzhinkin
force-pushed
the
bulk-api-part-2
branch
from
94e8786 to
2f3b57b
Compare
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.
This is a second portion of unsafe API described in #135.
This particular part aimed to facilitate the implementation of various
Bufferextensions.The implemented API was initially described in "2. Buffer iteration API" and "3. Byte-granular read/write API" subsections of #135 (comment)
This PR concludes the changes required to implement the API from #135, but our journey won't end here! The next patch in the queue is rewriting all existing extensions using the new API and then encapsulating all segments' internals.