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.

Sign up for GitHub

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

Jump to bottom

Deprecate StreamQueue.hasNext and StreamQueue.next #357

Closed
Cat-sushi opened this issue Oct 19, 2022 · 0 comments
Closed

Deprecate StreamQueue.hasNext and StreamQueue.next #357

Cat-sushi opened this issue Oct 19, 2022 · 0 comments
Labels
package:async

Comments

@Cat-sushi
Copy link

Cat-sushi commented Oct 19, 2022 •
edited
Loading

It is very unintuitive that await q.next just after await q.hasNext returning true might fail.
It is extremely unintuitive, almost insane, that q.hasNext.then((n) {print("4: $n");}) might print false.

You should remove those APIs completely, unless changing those behavior.

See also #356, #355, and dart-lang/sdk#50217.
@mosuem mosuem transferred this issue from dart-archive/async Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
package:async
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Cat-sushi @mosuem