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

.closed should be fulfilled/rejected after fulfillment/rejection of read()? #374

Closed
tyoshino opened this issue Jul 6, 2015 · 2 comments
Closed

.closed should be fulfilled/rejected after fulfillment/rejection of read()? #374

tyoshino opened this issue Jul 6, 2015 · 2 comments

Comments

@tyoshino
Copy link
Member

tyoshino commented Jul 6, 2015

My gut feeling is that pending read()s should be fulfilled/rejected first (to be precise; microtasks for fulfillment/rejection should scheduled first) in the same order in which they were called, and then .closed should be fulfilled/rejected.

Thoughts?
@domenic
Copy link
Member

domenic commented Jul 6, 2015

Hmm, this is a pretty minor detail, but it is something we need to decide and write tests for, I agree. I agree with you about the order.

@tyoshino
Copy link
Member Author

tyoshino commented Jul 7, 2015

Thanks. I'll go with that plan. This is FTR and to be used for discussion if anything new about this is found.

@tyoshino tyoshino closed this as completed Jul 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@domenic @tyoshino