News for hackers. Stuff that matters.

A comment on The Future of JavaScript. Parent comment

Re:The Future of JavaScript by tikhonj on Friday February 10, 2012 @03:35PM (#3577358)
There is a foreach that works: .forEach(). And when you're not just iterating over an array but transforming it, you have map(), reduce() and filter().
[ Parent | on HN ]
Re:The Future of JavaScript by herge on Friday February 10, 2012 @04:08PM (#3577490)
Is it really too much to ask to have some syntactic sugar. Is

    for i,v in blah
, where i is an index of an array, or a key (not a property!) of a dictionary really too much to ask in 2012?

No wonder people are using coffeescript.

[ Parent | on HN ]
Re:The Future of JavaScript by jashkenas on Friday February 10, 2012 @05:23PM (#3577738)
CoffeeScript's got you covered. Here's forEach ...

    for item, index in list
... here's the same over an object ...

    for key, value of object
... here's the map() ...

    mapped = for item in list
... here's the filter() ...

    filtered = for item in list when item.isActive
... and so on.
[ Parent | on HN ]
Re:The Future of JavaScript by herge on Friday February 10, 2012 @07:58PM (#3578191)
Exactly. The number one thing javascript should take from coffeescript is the iteration syntax.
[ Parent | on HN ]
Re:The Future of JavaScript by cmf028 on Saturday February 11, 2012 @01:21AM (#3578722)
ecmascript 6 will also introduce for of loops which is said to fix for in. checkout wiki.ecmascript.org for all the ecmascript 6/harmony niceness
[ Parent | on HN ]