-
Notifications
You must be signed in to change notification settings - Fork 13
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
%TypedArray%.fromAsync #8
Comments
I agree. I think this is within this proposal’s scope. |
Spec of |
I presented a brief update presentation about this issue to the Committee at the October plenary today. @syg of Google V8 voiced moderate opposition to including a TypedArray.fromAsync in this proposal, barring any clear use cases, since any dumps of a stream or other async iterables into a typed array would almost certainly be chunked, rather than yielding individual numeric values. In order to minimize the probability of Committee blockage of Stage 2 when I present this proposal again in a few months, I will drop TypedArray.fromAsync and defer it to a future proposal. |
It's an interesting precedent since now all array methods that can be applied to typed arrays added to typed arrays too. "A clear use case" could be, for example, async getting an array of ids (typed arrays are also about typing, not only about performance) from stripped 3rd party API one by one - my recent case. However, I agree that it can be delayed. |
All new
Array
methods that make sense for%TypedArray%
also added to%TypedArray%
. Seems makes sense to add a%TypedArray%
version.The text was updated successfully, but these errors were encountered: