On Tue, Feb 18, 2014 at 3:34 PM, Allen Wirfs-Brock
<allen at wirfs-brock.com> wrote:
>> Of course adding an extra internal slot to all DOM objects is not necessarily all that great either...  Though maybe we have to do that no matter what to prevent double-initialization.
>
> You don't necessary need a new slot to to use as an initialized flag. I most cases you can probably get away with using a "not yet initialized" token in some existing slot.

Mmm. Well, sure, I think we can avoid bloating every Array to
accomodate [[ArrayInitialisationState]], by optimizing for the case
where it is true. But when you've got information, ultimately it has
to be stored, somehow, somewhere.

More to the point, this adds an axis to the configuration space of
Array objects. That’s inelegant. It makes new kinds of bugs possible.
Now that we're talking about extending the pattern to the whole DOM,
it sounds worse than it did a few months ago. :-P

Fight complexity creep!

-j

On Tue, Feb 18, 2014 at 3:34 PM, Allen Wirfs-Brock <allen at wirfs-brock.com> wrote:
> You don't necessary need a new slot to to use as an initialized flag. I most cases you can probably get away with using a "not yet initialized" token in some existing slot.

Mmm. Well, sure, I think we can avoid bloating every Array to
accomodate [[ArrayInitialisationState]], by optimizing for the case
where it is true. But when you've got information, ultimately it has
to be stored, somehow, somewhere.

More to the point, this adds an axis to the configuration space of
Array objects. That’s inelegant. It makes new kinds of bugs possible.
Now that we're talking about extending the pattern to the whole DOM,
it sounds worse than it did a few months ago. :-P

Fight complexity creep!