News for hackers. Stuff that matters.
Re:Github Ruby Styleguide by look_lookatme on Wednesday December 12, 2012 @08:50AM (#4909991)
Agreed. It's just not worth it, especially with implicit return.
Re:Github Ruby Styleguide by sabat on Wednesday December 12, 2012 @01:39PM (#4911713)
They're not synonyms; "and" is not a more readable version of "&&".

As Avdi Grimm says: and and or, despite an apparent similarity to && and ||, have very different roles.

It's worth using "and" and "or", especially considering that && and || bind too tightly for some purposes. I try to avoid && and || unless I'm doing a specific boolean operation (e.g. x = foo || bar). Not for flow control, though.

If you really can't grok the logic, use parens.