| 07:56 | <Jack Works> | So in the latest round of JS-is-missing-features discourse, one request that stands out is for Jack Works ‘s Number.range/BigInt.range. I am wondering, how can we move that forward? Is it blocked on anything? The iterator helper has been stage 3 so I want to advance it in Jan 2023 tc39 meeting, but I forgot to add it to the agenda. I'll add it to the next meeting |
| 07:58 | <Jack Works> | ok hear me out: for await.concurrent[2] (item of asyncIter) { ... } to run the body of the for-await concurrently. equivalent to await asyncIter.map(item => {...}).bufferAhead(2).forEach(() => {}) except that the body of the for-await can still do stuff like break and return (which prevent further iterations of the loop from starting, though any which have already started still run to the end of the loop body) Yeah I want this and I tried to add it in await.ops proposal but failed |
| 14:27 | <littledan> | The iterator helper has been stage 3 so I want to advance it in Jan 2023 tc39 meeting, but I forgot to add it to the agenda. I'll add it to the next meeting What's the implementation status? |
| 18:09 | <bakkot> | littledan I assume that comment was "since iterator helpers advanced it is time to bring back Number.range, as an iterator" |
| 18:10 | <bakkot> | Number.range is not yet ready for implementations |