Rick Waldron (2013-08-28T21:40:07.000Z)
On Wed, Aug 28, 2013 at 11:02 AM, Forbes Lindesay <forbes at lindesay.co.uk>wrote:

>  It would be nice from a readability point of view if
> `iteratable.toArray()` could always be used as a substitute for
> `Array.from(iteratable)`.
>

Since both Array.from and [..spread] already covers every single iterable
and arraylike case now and forever, there is very little benefit (none?) in
also specifying a toArray method on the prototype of every object that is
capable of creating an iterable.

Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130828/a1929146/attachment.html>
domenic at domenicdenicola.com (2013-08-31T20:58:19.708Z)
On Wed, Aug 28, 2013 at 11:02 AM, Forbes Lindesay <forbes at lindesay.co.uk> wrote:

>  It would be nice from a readability point of view if
> `iteratable.toArray()` could always be used as a substitute for
> `Array.from(iteratable)`.

Since both `Array.from` and `[..spread]` already covers every single iterable
and arraylike case now and forever, there is very little benefit (none?) in
also specifying a `toArray` method on the prototype of every object that is
capable of creating an iterable.