@@initialize, or describing subclassing with mixins
jussi.kalliokoski at gmail.com
Fri Jul 4 09:15:03 PDT 2014
On Tue, Jul 1, 2014 at 4:06 AM, Boris Zbarsky <bzbarsky at mit.edu> wrote:
> On 6/30/14, 3:38 PM, Jussi Kalliokoski wrote:
>> On Mon, Jun 30, 2014 at 10:16 PM, Boris Zbarsky <bzbarsky at mit.edu
>> Would it help the discussion if UA implementors described how they
>> solve these problems now?
>> Yess, please! +9999
> right-types/?answer=851#post-id-851 for Gecko.
> I'd be curious to hear what other UAs do.
Thanks for the link! Me too. :)
> As I suggested in one approach, for "natural" instances (in lack of a
>> better word) of Nodes can have all the in-memory layout optimizations
>> they need.
> Some of these are not just optimizations; some of these are needed for
> correctness. For example, we use fixed parts of the object layout to cache
> values for some Web IDL properties that need to keep returning the same
> thing over and over again.
I might be missing something, so is there something in the idea I proposed
that would prevent doing this?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss