Object comprehensions: "for key, value" would feel more natural about coffeescript HOT 3 CLOSED

Nope, not a bug in the docs. The problem is the equivalence between object and array comprehensions -- at the moment they both compile into the same code body (because we don't know if a variable is an object or an array at compile time). So, it was thought to be nicer to have:

for value, index in array
for value, key in object

This is the same API as the Underscore.js collection functions (each, map, reduce), and also the same argument order as forEach and map in JavaScript 1.6

from coffeescript.

Well, ok then :-)

from coffeescript.

Alright. Closing the ticket. If someone finds a way to cleanly distinguish between the two at runtime (without generating too much code or violating the no-special-functions rule), we can reopen it.

from coffeescript.