@/be > No, we do not want normative spec language requiring a per-object > private-named property that determines the > Object.prototype.toString.call(x).slice(8,-1) result. > > Doing this naively will both impose unacceptable overhead *and* allow > type-confusion attacks.
I'm talking about adding back the wording that ES5.x currently has allowing host objects to set their own internal [[Class]] (or whatever it's new incarnation is) value. Most objects will still have an internal [[NativeBrand]] property of some kind associated with them so I don't see how this is an overhead concern. > Not at the price of per-instance "class-name". The current ES6 draft handles this by allowing objects to *not* have a [[NativeBrand]] property specified as `Object#toString` will simply return "[object Object]". - JDD _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
