rails/rails — comment on commit 4ef74536940ea4c8c7f8c2cb0252bfe5f0db6fdf
File:  line 0
By mkdynamic:

Appreciate your response, and following Rails' conventions totally makes sense.

Re: inline conditionals, I personally don't have a strong feeling, but I understand the argument that it is a style which is slightly more vulnerable to accidental assignment vs. equality errors. Anyway, it's a waste of time debating that imo.

I don't see any specific reference to not using `and`, although I am very likely looking in the wrong place:
http://guides.rubyonrails.org/contributing_to_ruby_on_rails.html#follow-the-coding-conventions

Avoiding `and` makes sense in any case. The precedence difference is too subtle and potentially confusing. I don't think it reads clearly most of the time either.