Brendan Eich (2013-10-01T17:33:15.000Z)
domenic at domenicdenicola.com (2013-10-13T02:47:05.756Z)
Allen Wirfs-Brock wrote: >> Currently, that works for everything but null >> and undefined, so I assume that this pattern is used quite a bit. > > Do you think it really is? I don't. (That is, I don't see much x.toString() feeding into bracketed property lookup, if any.) Explicit .toString() calling is rare because verbose, in addition to throwing on null and undefined. People use + ''. But that's covered, and I say if someone has a symbol named x (whether they know it's a symbol or "any") and they call .toString(), they should get what they're asking for: throw on null or undefined (or a misbehaving impl), otherwise a string.