On Tue, Dec 16, 2014 at 9:59 PM, Anne van Kesteren <[email protected]> wrote: > > On Tue, Dec 16, 2014 at 9:43 PM, Dmitry Lomov <[email protected]> > 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 some optimizations for small typed arrays) - frankly I expect > this > > to be a long tail of work. > > This was actually part of my concern. If you don't ship this > refactoring, we won't know whether this refactoring of builtins is web > compatible. And if we later find out it's not and requires changes to > the way subclassing is done in general, what can we do? >
Before we ship anything we need to implement it, so I am sorry Anne that me and other engineers working on this feature fell short of your high expectations here :) Seriously though, making bulitins subclassable is quite a lot of work in the engine (I have to point out again that in particular [[CreateAction]] and exposure of un-(or, rather semi-)initialized bulitins makes implementation much more complex that it might have been). As in any project, we have to prioritize what features we are working on when, and as in any project we have a limited number of available qualified hackers. What would you prefer, arrow functions or an ability to subclass Date? Dmitry -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
