James Browning
James Browning
Ditto for `super.method` when within a method-type function.
What you're asking for is already at stage 2: https://github.com/tc39/proposal-iterator-helpers
> Awesome news, thanks! It's a little unclear from that proposal that you'll be able to do: Not if `urls` is an `Array`, but you can just wrap it using...
> If it's an array you can do `urls.values().reduce(...)` That won't work for the given example, as then the `sum` argument would be a promise as `urls.values()` is a sync...
> have an array of promises that I need to resolve them one by one. An array (or sync iterable) of promises if more of a bonus, the primary usage...
Also when combined with async generators, you can create some fairly efficient lazy structures (and **really** easy to write once you know how), for example in Node.js suppose you wanted...
> // Once we have run passing this await the fetch request has resolved, in the current implementation > // I will get the all data in response.body, I need...
I feel like it would simpler to go with one of the previous ideas where there was an actual `Global` constructor that made new global objects. This means the host...
> Nevermind this, I thought `.constructor` was an own property on builtin functions, but it's actually just inherited from `Function.prototype.constructor`. Actually no this is still a problem, `Array.constructor` can't be...
> the information i'd prefer to avoid exposing is "whether a module uses import.meta" - otherwise that becomes a part of the module's API, and starting to use it, or...