4 ms·
This is one reason why I always use parens on my method calls. Some rubyists find it cluttering, yeah, but I think it makes reading code easier. The other one
by andrewvc 16y ago
This is one reason why I always use parens on my method calls. Some rubyists find it cluttering, yeah, but I think it makes reading code easier.
The other one to watch out for is precedence of {} vs do; end. Example:
> x = [1,2].map do |i| i*2; end
=> [2, 4]
> puts [1,2].map do |i| i*2; end
1
2
=> nil
> puts [1,2].map { |i| i*2}
2
4
=> nil
- jashkenas 16y agoAgreed. It's why we've tried to be careful with lambda/hash/call syntax in CoffeeScript, especially where some of it is optional, and can be left out. For example: x = [1, 2].map (i) -> i * 2 ... is without optional parens. x = [1, 2].map((i) -> i * 2) ... is with them. configure start: 10, end: 25 ... is the syntax for calling a method and passing an implicit hash -- and with the optional braces and parens added, it's closer to JavaScript... configure({start: 10, end: 25})