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

improve ByteBuffer documentation regarding CoW on slices #359

Merged
merged 3 commits into from
Apr 26, 2018

Conversation

weissi
Copy link
Member

@weissi weissi commented Apr 26, 2018

Motivation:

We got a very valid question on Twitter
(https://twitter.com/karim_elna/status/989516133421199361) regarding
ByteBuffers 'sharing storage'. Our docs almost sound like a ByteBuffer
and its slices share storage even after a write. Especially given that
this is a difference to Netty, we should document this better.

Modifications:

Added clarifying documentation.

Result:

Hopefully the docs are more clear now.

Motivation:

We got a very valid question on Twitter
(https://twitter.com/karim_elna/status/989516133421199361) regarding
ByteBuffers 'sharing storage'. Our docs almost sound like a ByteBuffer
and its slices share storage even after a write. Especially given that
this is a difference to Netty, we should document this better.

Modifications:

Added clarifying documentation.

Result:

Hopefully the docs are more clear now.
Copy link
Contributor

@Lukasa Lukasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@normanmaurer
Copy link
Member

@swift-nio-bot test this please

@normanmaurer normanmaurer merged commit 5d3aa22 into apple:master Apr 26, 2018
@normanmaurer normanmaurer added this to the 1.6.0 milestone Apr 26, 2018
@weissi weissi added the semver/patch No public API change. label Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants