On Wed, Oct 1, 2014 at 12:59 PM, Rick Waldron <waldron.rick at gmail.com>
wrote:

>
>
> On Wed, Oct 1, 2014 at 3:51 PM, Jeremy Martin <jmar777 at gmail.com> wrote:
>
>> Not sure if this is sufficient motivation to accelerate the timeline
>>
>
>
> It's not about "motivation", it's about realistic time constraints. TC39
> has already had to push out 6 months and that was not taken well by both
> the community and by Ecma. Further delay is not an option.
>
>
Just out of curiosity: what's the realistic "out of time" issue here?
Actually, I think having a ready and working algorithm draft on github gist
will help discussing this faster and in realistic time frames (I've
should've done before starting this thread; otherwise, these are "too
abstract time-stoppers" for me -- unless you know specific big issues that
will be hard to implement).


>
>
>> for adding suitable parallels from Array.prototype, but it may be worth
>> recalling what developers did last time there were obvious "gaps" in what a
>> native prototype provided.  Array#contains, anyone?
>>
>
> As a community we'll simply have to reject the use of code that directly
> modifies built-ins. This is also not a very strong argument in the ES6
> world where built-ins can be subclassed.
>
>
Actually the case with "borken" `Array#contains` which is so actively
discussed, is a good example. I think very likely `Map#map`, and
`Map#filter` will be added manually if not in ES6.

Dmitry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20141001/9547172b/attachment-0001.html>

> It's not about "motivation", it's about realistic time constraints.

Just out of curiosity: what's the realistic "out of time" issue here?
Actually, I think having a ready and working algorithm draft on github gist
will help discussing this faster and in realistic time frames (I've
should've done before starting this thread; otherwise, these are "too
abstract time-stoppers" for me -- unless you know specific big issues that
will be hard to implement).

> As a community we'll simply have to reject the use of code that directly
> modifies built-ins.

Actually the case with "borken" `Array#contains` which is so actively
discussed, is a good example. I think very likely `Map#map`, and
`Map#filter` will be added manually if not in ES6.