Skip to content

Conversation

@JakeWharton
Copy link
Contributor

This allows the caller to more easily perform their own bookkeeping based on the amount of bytes moved.

Closes #360

This allows the caller to more easily perform their own bookkeeping based on the amount of bytes moved.
@fzhinkin fzhinkin self-requested a review August 12, 2024 17:29
Copy link
Collaborator

@fzhinkin fzhinkin left a comment

Choose a reason for hiding this comment

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

The change itself looks good, but I think we should also update JVM-specific extensions.
For readFromHead and writeToTail the change should be trivial as they delegate to common functions.
For readBulk it should be trivial too, we just have to use Long instead of Int there.

@JakeWharton
Copy link
Contributor Author

Indeed. Done.

@fzhinkin
Copy link
Collaborator

@e5l FYI: formally, that's a breaking change, but Ktor (the only user of the API published on GH) should be unaffected since updated functions are all inline functions.

Copy link
Collaborator

@fzhinkin fzhinkin left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks!

@fzhinkin fzhinkin merged commit d7b0533 into Kotlin:develop Aug 14, 2024
@JakeWharton JakeWharton deleted the jw.return-byte-count.2024-07-31 branch August 15, 2024 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants