W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: Custom element design with ES6 classes and Element constructors

From: Gabor Krizsanits <gkrizsanits@mozilla.com>
Date: Tue, 13 Jan 2015 18:06:24 +0100
Message-ID: <CAMXCnK8DYNEyVcAp=wP0P1t4HsQqt7akkfhS__+8a-pznAu=HA@mail.gmail.com>
To: public-webapps@w3.org
> I think this part of the spec was largely written before ES6 class stuff
> stabilized, fwiw.  Which is not hard, since it's still not stabilized.  ;)
Isn't there a chance to consider our use-case in ES6 spec. then?

> Basically, ES6 is moving toward coupling allocation and
> initialization but the upgrade scenario can't really be expressed by
> coupled alloc+init if it preserves object identity, right?

Yes, and it seems to me that we are trying to hack around the fact that
ES6 classes are not compatible with what we are trying to do. Would
it be naive to request a well defined way to change an objects class
post alloc? It seems like a hard problem, but I can imagine
pure JS cases too when it would make sense to do a transformation.

And if there is no official way to do it people will start to try
and hack their way through in 1000 horrible ways...

(+ internally I'm sure most engines does transformations in some cases
already, like for array optimisations...)

 - Gabor
Received on Tuesday, 13 January 2015 17:06:52 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC