On Tue, Dec 16, 2014 at 9:59 PM, Anne van Kesteren wrote:
>
> On Tue, Dec 16, 2014 at 9:43 PM, Dmitry Lomov
> wrote:
>
> > True for plain ES6 classes. Less true for bulitins implementation-wise
> (fair
> > amount of work and possible bug farm, for quite diminishing returns;
> likely
> > loss of s
On Tue, Dec 16, 2014 at 9:02 PM, Allen Wirfs-Brock
wrote:
>
>
> On Dec 16, 2014, at 11:25 AM, Dmitry Lomov wrote:
>
>
>
> On Tue, Dec 16, 2014 at 7:04 PM, Allen Wirfs-Brock
> wrote:
>>
>>
>>
>> The V8 concern seems to be about hypothetical that aren't actually in the
>> Es6 specification. Anythi
On Dec 16, 2014, at 11:25 AM, Dmitry Lomov wrote:
>
>
> On Tue, Dec 16, 2014 at 7:04 PM, Allen Wirfs-Brock
> wrote:
>
>
> The V8 concern seems to be about hypothetical that aren't actually in the Es6
> specification. Anything other than the [[CreateAction]]'s defined in the ES6
> spec. a
On Tue, Dec 16, 2014 at 7:04 PM, Allen Wirfs-Brock
wrote:
>
>
> On Dec 16, 2014, at 9:19 AM, Domenic Denicola wrote:
>
> > From: blink-...@chromium.org [mailto:blink-...@chromium.org] On Behalf
> Of al...@wirfs-brock.com
> >
> >> Let me turn this around on you. What in the current draft prevents
On Tue, Dec 16, 2014 at 6:08 PM, wrote:
>
>
>
> On Tuesday, December 16, 2014 2:50:40 AM UTC-8, Dmitry Lomov wrote:
> ...
>>
>>
>>
>>> Is there a concrete plan for proposing something else, or is the
>>> concrete plan to simply never allow subclassing of builtins? Because
>>> that's the one con
On Dec 16, 2014, at 9:19 AM, Domenic Denicola wrote:
> From: blink-...@chromium.org [mailto:blink-...@chromium.org] On Behalf Of
> al...@wirfs-brock.com
>
>> Let me turn this around on you. What in the current draft prevents you from
>> implementing object allocation lazily exactly as you des
On Tuesday, December 16, 2014 2:50:40 AM UTC-8, Dmitry Lomov wrote:
...
>
>
>
>> Is there a concrete plan for proposing something else, or is the
>> concrete plan to simply never allow subclassing of builtins? Because
>> that's the one concrete option 3 here, and it's not a very palatable
On Tue, Dec 16, 2014 at 11:07 AM, Boris Zbarsky wrote:
>
> On 12/16/14, 1:56 AM, Dmitry Lomov wrote:
>
>> the problem with this option is that between entry to the constructor
>> and call to super(...) `this` is necessarily an exotic ImageData in some
>> sort of semi-initialized state.
>> That sem
On Mon, Dec 15, 2014 at 10:22 PM, Anne van Kesteren
wrote:
>
> On Mon, Dec 15, 2014 at 3:15 PM, Dmitry Lomov
> wrote:
> > - At this time we do not support subclassing built-ins and DOM objects
>
> If you don't ship this part, isn't there quite a big risk that we
> might find out too late that the
