W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2015

[Bug 28244] Requiring @@toStringTag on instances may have performance implications

From: <bugzilla@jessica.w3.org>
Date: Thu, 19 Mar 2015 17:50:50 +0000
To: public-script-coord@w3.org
Message-ID: <bug-28244-3890-Uk21sjWnAd@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28244

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bzbarsky@mit.edu

--- Comment #1 from Boris Zbarsky <bzbarsky@mit.edu> ---
> calls for a @@toStringTag own property on each object instance implementing an
> interface

This is just because we want different toString() results for Node instances
and Node.prototype, right?

I agree that putting this on all instances is totally undesirable.

Hanging it off the prototype with an accessor means that the
Object.prototype.toString value changes if you munge the proto chain.  Maybe
that's OK.

The pseudocode in comment 0 doesn't work that well for cross-origin invocation
of various sorts, but that could be solved in spec prose.

In some ways, what would be ideal here is having a more extensible way to hook
into toString via branding, the way ES6 does for the objects _it_ defines.... 
Certainly that's how DOM toString stuff is implemented right now and has been
for a long time, and I have some web compat worries about changing it. :(

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 19 March 2015 17:50:51 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 March 2015 17:50:51 UTC