Yeah, it seems like kind of an odd choice to introduce a whole new type *and* ex... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

bcoates on June 12, 2015 | parent | context | favorite | on: ES6 in Depth – Symbols

Yeah, it seems like kind of an odd choice to introduce a whole new type and extend the kind of values that can index an object, when extending object indexing alone would do everything symbols do anyway.

quarterto on June 12, 2015 [–]

It's actually not extending object indexing. From the object's point of view, the symbol is just another (albeit opaque) string.

bcoates on June 12, 2015 | [–]

There's still some magic involving the symbol properties being automatically non-enumerable, right?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact