« Bugzilla Issues Index

#1546 — Symbol type not handled in Object constructor needs to be updated to handle the new primitive Symbol type.

I'm going to revert to specifying Symbol as an exotic objects. Treating it as a new primitive types just creates too many places where it needs to be explicitly dealt with and sets the wrong precedent for future extensible value types based upon immutable objects. However, typeof Symbol() will still be "symbol".

fixed in rev 16 editor's draft

Symbols are again Objects

fixed in rev16 draft. July 15, 2013