Feature proposal

Isiah Meadows isiahmeadows at gmail.com
Fri Jul 20 00:32:04 UTC 2018

I'm not a fan of the "Iteratable" object - it doesn't align with the
corresponding existing concept of "iterables", and the iterable
protocol is just an interface - there's no named object that
corresponds to that type.

What we really need is that pipeline operator to finally get figured
out: https://github.com/tc39/proposal-pipeline-operator

That wil address the primary need for things like these, without
running you into issues of namespace collision.


Isiah Meadows
me at isiahmeadows.com

On Thu, Jul 19, 2018 at 11:38 AM, Nicolas B. Pierron
<nicolas.b.pierron at mozilla.com> wrote:
> On Thu, Jul 19, 2018 at 12:53 PM, Nicolas B. Pierron
> <nicolas.b.pierron at mozilla.com> wrote:
>>> On Wed, Jul 18, 2018 at 2:06 PM Nicolas B. Pierron
>>> <nicolas.b.pierron at mozilla.com> wrote:
>>>> Stupid question, but why are some of these methods implemented on
>>>> String, Array, TypedArray, Map and Set, while all of them are
>>>> Iteratable?
>> Among list of nice Iteratable property that one might add, and which
>> might not be part of the standard are things like:
>>   chain, take, skip, takeWhile, skipWhile, repeat, zip, enumerate,
>> range, stepBy, …
> Apparently this already exists as a JS library:
> https://fitzgen.github.io/wu.js/
> --
> Nicolas B. Pierron

More information about the es-discuss mailing list