Andreas Rossberg wrote:
On 17 July 2013 21:10, Brendan Eich<[email protected]> wrote:
We should not add more such user-facing pain if we can avoid it -- even if
that means more implementor-facing pain (remember Mr. Spock's Kobayashi Maru
solution ;-).
An inconsistency between strings and symbols is both a user-facing and
an implementor-facing pain.
Strings and symbols are quite different according to typeof and
behavior, in any proposal or implementation. How does providing a
wrapper which when used throws -- unlike ({}[new String('x')]) which
does not throw -- help make symbol like string in any user-facing sense?
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
