The class operator: a bridge between object and function exemplers

Brendan Eich brendan at
Tue Nov 15 14:45:32 PST 2011

On Nov 15, 2011, at 10:34 AM, Russell Leggett wrote:

> Yes, of course you're right about that. There was something in the back of my brain saying there might be a problem with that optimization, but I had hoped it could be done, because that is probably the most common case.  I suppose you could say that it isn't an optimization, but simply part of the semantics. Not sure if that would be confusing or just seem like the right behavior.

Semantics that sometimes make a new object with the given operand as its proto, other times return the operand unobservably mutated, are not gonna fly. That's bad for human and robot readers (i.e., implementations).


More information about the es-discuss mailing list