Sharing machinary with iterator-helpers toArray

[benjamingr]

Hey, I was wondering, since Array.fromAsync(iter) is similar to AsyncIterator.from(iter).toArray() wouldn't it make sense if they shared the same spec text? That is one (for example fromAsync) is defined and the other is defined in terms of it?

(I agree that it makes sense to have both as it's more ergonomic and people will likely reach out to both - though that's not the discussion here)

[ljharb]

Certainly it'd be ideal if they shared steps via abstract operations, but that'd likely happen after one of them had landed in the main spec.

[benjamingr]

That sounds reasonable to me.

[zloirock]

For sharing this logic, this difference should be resolved tc39/proposal-iterator-helpers#168. At this moment, core-js use one internal operation for them.

[js-choi]

We will discuss this issue (as well as #19 and tc39/proposal-iterator-helpers#168) when we present this proposal for Stage 3 at the upcoming plenary meeting.

We could try isolating the algorithm into its own abstract operation soon in anticipation of iterator-helpers. It’s just an editorial thing.

Related: #1, #19, tc39/proposal-iterator-helpers#36, tc39/proposal-iterator-helpers#142, tc39/proposal-iterator-helpers#156.

[bakkot]

Since AsyncIterator is an earlier-stage proposal I don't think there's anything to do here.

[js-choi]

Closing this in lieu of tc39/proposal-async-iterator-helpers#28.