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

v2.3.0 #94

Merged
merged 1 commit into from
Mar 17, 2024
Merged

v2.3.0 #94

merged 1 commit into from
Mar 17, 2024

Conversation

notgull
Copy link
Member

@notgull notgull commented Feb 24, 2024

@notgull
Copy link
Member Author

notgull commented Feb 25, 2024

Build failure is #95

@taiki-e
Copy link
Collaborator

taiki-e commented Feb 26, 2024

@notgull
Copy link
Member Author

notgull commented Feb 29, 2024

Hmm, good point. What if we called it ready_for(&stream) instead?

@notgull notgull changed the title v2.2.1 v2.3.0 Mar 2, 2024
@taiki-e
Copy link
Collaborator

taiki-e commented Mar 3, 2024

ready_for

Hmm, "ready" is already used in multiple meanings... (task::ready!, future::ready)

@notgull
Copy link
Member Author

notgull commented Mar 3, 2024

Scattershot other suggestions:

  • stream_iter
  • immediate
  • poll_once

@i509VCB
Copy link

i509VCB commented Mar 4, 2024

drain might work quite well.

Drain would also match the semantics around Vec::drain which is an iterator that also removes every element from the container.

CHANGELOG.md Outdated Show resolved Hide resolved
Signed-off-by: John Nunley <dev@notgull.net>
@notgull notgull requested a review from taiki-e March 16, 2024 17:37
@notgull notgull merged commit cdf5d64 into master Mar 17, 2024
7 checks passed
@notgull notgull deleted the notgull/next branch March 17, 2024 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants