-
Notifications
You must be signed in to change notification settings - Fork 33
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
Awaiting of IteratorValue
in %AsyncIteratorPrototype%
methods
#168
Comments
Async iterator helpers should be awaiting the value too, I’d expect. |
I would expect the behavior to be the same as async iterators in `for await. That is, tc39/proposal-async-iteration#15 (unfortunately, I don't particularly like this behaviour). |
I agree with the OP that they should match. I like the behavior currently in this proposal, which is what you'd get with |
Closing as nothing to do here. |
@michaelficarra why? It's still not aligned between both proposals and the inconsistency should be resolved. |
@zloirock The inconsistency can be resolved by this proposal remaining unchanged and the |
@michaelficarra as you can see, they (at least @ljharb and @js-choi) decided to change the behavior that's used here. So, please, instead of ignoring this issue, align it - I don't care on what side. I'm (and it seems all the rest) pretty sure that those methods should use one approach. |
For what it’s worth, I’ve come around to the old behavior of Array.fromAsync, which matches the iterator-helpers spec. See tc39/proposal-array-from-async#19 (comment). |
See the original issue in the
Array.fromAsync
proposal. The same is applicable to%AsyncIteratorPrototype%
methods.I think that it should be agreed upon between both proposals.
The text was updated successfully, but these errors were encountered: