Skip to content
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

Unsafe API: make segment size and remaining capacity public #408

Open
fzhinkin opened this issue Oct 30, 2024 · 0 comments · Fixed by #409
Open

Unsafe API: make segment size and remaining capacity public #408

fzhinkin opened this issue Oct 30, 2024 · 0 comments · Fixed by #409

Comments

@fzhinkin
Copy link
Collaborator

Proposed Unsafe API design explicitly mentioned availability Segment.size and Segment.remainingCapacity properties.
Moreover, some of our samples use these properties.
However, properties themselves remain internal.

Without having access to these properties it is quite hard to reason about number of bytes that could be read from or written to a segment using Unsafe API, thus we need to make them public.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant