Optional curlies around objects as method parameters about coffeescript HOT 4 CLOSED

Right, that's the problem -- it's already valid CoffeeScript. Aspects of this have been addressed in:
http://github.com/jashkenas/coffee-script/issues/closed#issue/16
Which deals with default arguments.

The problem with having things look like named arguments is that they're not, really. Instead of getting them as optional local variables within the function, you have to look inside of the options hash. I think that this is an important distinction to have, especially because there's no reason why CoffeeScript couldn't support real named arguments (if the ambiguity with the assignment syntax can be worked out).

from coffeescript.

TBH - I think it's best to avoid thing like this as it makes the model harder to understand. One of the nice things about Javascript is that there aren't too many rules about it's syntax.

from coffeescript.

You're both right, I'll close this issue. Missed the closed issue, sorry.

BTW: holy crap! splats! That's so awesome, CoffeeScript rocks!

from coffeescript.

It's all good. It's great to have this stuff on record, so people can read through the discussion. If you're looking to see what the limits of the syntax are, I'd recommend reading through the scripts in tests/fixtures/execution. That's the bulk of the current test suite -- each test should only compile lintlessly, and only ever print "true".

from coffeescript.