Le 12 août 2014 à 22:35, Erik Arvidsson <erik.arvidsson at gmail.com> a écrit :

> Right now String(symbol) throws because it uses ToString which is spec'ed to throw.
> 
> I'm suggesting that we special case String(value) to do a type check for Symbol and return the same string as Symbol.prototype.toString.call(value) does.
> 
> https://people.mozilla.org/~jorendorff/es6-draft.html#sec-string-constructor-string-value
> 
> The motivation for this is that String(value) is pretty explicit and was in ES5 a safer way to stringify something than value.toString().
> 
> -- 
> erik

+1. As I already noted last year [1], as currently specced, ad-hoc debugging code like `alert("got argument: " + x)` or `alert("got argument: " + String(x))` will throw for symbols, while `alert("got argument: " + x.toString())` will throw for `null`, `undefined`, and `Object.create(null)`.

[1] http://esdiscuss.org/topic/a-new-es6-draft-is-available#content-11


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140812/d1707ae0/attachment.html>

+1. [As I already noted last year][1], as currently specced, ad-hoc debugging code like `alert("got argument: " + x)` or `alert("got argument: " + String(x))` will throw for symbols, while `alert("got argument: " + x.toString())` will throw for `null`, `undefined`, and `Object.create(null)`.

[1]: http://esdiscuss.org/topic/a-new-es6-draft-is-available#content-11