@@toStringTag spoofing for null and undefined

[Brendan Eich]

Allen Wirfs-Brock wrote:
> There is no such thing as a symbol valued property key that is not exposed via reflection.

Sure -- the idea was to make the symbol spec-internal, even use an 
abstract operation rather than a symbol -- anything to provide a spec 
hook for WHATWG/W3C specs to build on, without overcommitting.

Calling @@toStringTag a "solid win" is premature. We can extend in many 
ways to allow the platform to be explained better in self-hosted JS. 
That does not mean a configurable non-writable property, "~"-prefixing, 
the whitelist.

We need to come to consensus on the ES6 details, implement, user-test, 
before declaring victory (solid, liquid, or gaseous). There are many 
putative solid wins in the multiverse. Lack of consensus strongly 
suggests specifying less, deferring (not "throwing away").

/be