27553 2014-12-10 13:10:47 +0000 Support Symbol 2017-12-06 11:12:56 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC All RESOLVED WORKSFORME P2 normal --- 1 annevk d bzbarsky d erik.arvidsson mike public-script-coord public-webapps-bugzilla oldest_to_newest 116091 0 annevk 2014-12-10 13:10:47 +0000 JavaScript can now define unique keys. Platform should have that ability as well. 116108 1 bzbarsky 2014-12-10 19:51:11 +0000 Which parts of this do we need in IDL? Presumably we need to have a way for "SomeInterface.something" to be a well-known symbol (well-known in the sense that SomeInterface.something === otherWindow.SomeInterface.something), right? Do we need anything else? Do we need the ability to put these symbols on Symbol instead of SomeInterface? (I'd say we don't want that, personally.) 116109 2 annevk 2014-12-10 21:20:14 +0000 Only SomeInterface, Symbol is for TC39. (Although this will get messy of course once they adopt something from DOM again.) 116110 3 bzbarsky 2014-12-10 21:31:36 +0000 OK. So we could support syntax like so: interface Foo { symbol xyz; } which would make Foo.xyz a well-known symbol whose [[Description]] is "Foo.xyz", right? Do we also need the ability to have symbol-named things on dictionaries or something? 116975 4 erik.arvidsson 2015-01-09 20:11:32 +0000 Should probably be: interface Foo { static Symbol xyz; } and then the rules for Symbol would have to define that all code realms need to share the Symbol xyz, just like ES6 defines the well known symbols: http://people.mozilla.org/~jorendorff/es6-draft.html#sec-well-known-symbols 128999 5 annevk 2017-12-06 11:12:56 +0000 Part of this got addressed by https://github.com/heycam/webidl/pull/377. If the other part is still needed it's probably best to file a new issue for that. It's unclear at this point whether there are use cases.