[Bug 27346] Data properties


Domenic Denicola <d@domenic.me> changed:

           What    |Removed                     |Added
                 CC|                            |d@domenic.me

--- Comment #3 from Domenic Denicola <d@domenic.me> ---
> The main problem here would actually be that afaict creation of an object with data properties would be slower than of one without, since you have to set up the data properties on it (unlike the current Web IDL accessors, which actually live on the prototype, so only have to be set up once, not per object).

Can you help me understand why? I've always been curious. It seems like (for
the cases where there's really per-instance state, at least) you'd need to
store the per-instance state somewhere anyway. I.e., why is it different to
have an "internal slot" on the object + a getter on the prototype, vs. a data
property on the object?

You are receiving this mail because:
You are on the CC list for the bug.

Received on Monday, 17 November 2014 15:27:30 UTC