-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
object literal extensions not working with --es_staging/--harmony flags #685
Comments
Also what you want is consider a separate feature - "computed property names": https://code.google.com/p/v8/issues/detail?id=3754 |
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: