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

Do not store items field in ReadyChunks #2656

Merged
merged 1 commit into from
Oct 22, 2022

Conversation

stepancheg
Copy link
Contributor

@stepancheg stepancheg commented Oct 22, 2022

items is always empty when poll_ready exits, so there's no reason to store it inside ReadyChunks.

This does not solve practical issues, but makes code easier to understand.

`items` is always empty when `poll_ready` exists, so there's no
reason to store it inside `ReadyChunks`.

This makes code a bit more efficient, but also makes code easier
to understand.
Copy link
Member

@taiki-e taiki-e left a comment

Choose a reason for hiding this comment

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

Thanks!

@taiki-e taiki-e merged commit 8cfc085 into rust-lang:master Oct 22, 2022
@stepancheg stepancheg deleted the ready-chunks branch October 22, 2022 11:18
taiki-e pushed a commit that referenced this pull request Jan 30, 2023
`items` is always empty when `poll_ready` exists, so there's no
reason to store it inside `ReadyChunks`.

This makes code a bit more efficient, but also makes code easier
to understand.
taiki-e pushed a commit that referenced this pull request Jan 30, 2023
`items` is always empty when `poll_ready` exists, so there's no
reason to store it inside `ReadyChunks`.

This makes code a bit more efficient, but also makes code easier
to understand.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants