You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason, Object literal extensions involving Symbols (like creating your own @@iterable) doesn't seem to be working; an example of usage that works within 6t05, Traceur, and es6fiddle.net is below this paragraph as a code snippet:
Here's successful example running within ES6 Fiddle I've screen captured as well:
Seemingly, including the fact literal shorthands of declaring properties also doesn't work for me with iojs at the moment, the docs may need to be edited to omit Object literal extensions being covered by --es_staging or --harmony
The error typically thrown by iojs when running scripts attempting to use object literal extensions is screen captured below:
The text was updated successfully, but these errors were encountered:
Then there are staged features which are almost-completed features that haven't been completely tested or updated to the latest spec yet and therefore are not considered stable by the V8 team (e.g. there might be some edge cases left to discover)
I also ran into this issue. The official ES6 docs for io.js link to here which includes computed property names in enhanced object literals. It could probably be made more clear that they aren't supported in io.js yet.
For some reason, Object literal extensions involving Symbols (like creating your own
@@iterable
) doesn't seem to be working; an example of usage that works within6t05
,Traceur
, and es6fiddle.net is below this paragraph as a code snippet:Here's successful example running within ES6 Fiddle I've screen captured as well:
Seemingly, including the fact literal shorthands of declaring properties also doesn't work for me with iojs at the moment, the docs may need to be edited to omit Object literal extensions being covered by
--es_staging
or --harmonyThe error typically thrown by iojs when running scripts attempting to use object literal extensions is screen captured below:
The text was updated successfully, but these errors were encountered: