On Tue, Dec 16, 2014 at 11:19 PM, Boris Zbarsky <[email protected]> wrote: > > On 12/16/14, 1:56 AM, Dmitry Lomov wrote: > >> Option 2: pass arguments to [[CreateAction]] hook. >> [[CreateAction]] hook is the hook that is invoked directly before >> construction, and has access to constructor arguments. >> > > Dmitry, > > I finally have all this stuff paged in again. Sending one last mail here > to make sure we're on the same page, and my apologies for hijacking your > lists. > > So if I recall correctly, the setup with [[CreateAction]] is meant to > allow subclassing of builtins without requiring implementations to expose > uninitialized builtin objects, with the restriction you mention: the > constructor arguments have to have the builtin constructor arguments as a > prefix. > > I _believe_ the idea is that this allows some subclassing of builtins and > that once we (TC39 + WebIDL) have sorted out how to do whatever it is we're > doing in ES7 we can loosen the argument order restriction without breaking > anything that's already using the current setup.
> I know you think the argument order restriction is unacceptable, but it's > not being proposed to stay long-term. > Nothing is more permanent than temporary measures, as the saying goes. [[CreateAction]] with arguments is clearly a wrong design, and until we see a clear path for removing the argument order restriction, it is irresponsible to ship a broken thing with no recourse. 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.
