If `foo == bar` evaluates to true, the `or` is short-circuited, else it calls the built-in `die` function which kills the process.
@current_user.logged_in? or redirect_to login_path
@current_user.can? :do_this or render :status => 403
shirt.blue? and return bar
put_suit_on or put_pants_on shirt.blue? and return bar
would be equivalent to return bar if shirt.blue?
You can do the same with or and unless.if first_user = User.find(4) && second_user = User.find(6) ... end
It looks like it would evaluate as: first_user = (User.find(4) and second_user = User.find(6))
That is to say, the assignment comes after the boolean operation, which is unexpected.
first_user = User.find(4) && second_user = User.find(6)
to be literally equivalent to second_user = User.find(6)
first_user = User.find(4) && second_user
I honestly can't see why you might want it to mean something else...Edit: I see. if you do something like
if (first_user = User.find(4) && second_user = User.find(6)) {
..
}
it might bite you. You might expect it to be equivalent to first_user = User.find(4)
second_user = User.find(6)
if (first_user && second_user) {
..
}
which I personally think is a very, very bad practice. Parenthesis should always be used when there's even the slightest possibility that you or another maintainer/contributor might be confused about.Having an assignment that could be skipped by short-circuiting also seems like bad practice, but I realize it was designed to be a toy example
first_user = User.find(4) if first_user second_user = User.find(6) if second_user ... end end
Yes, but you can make the same point in favor of using "and" and "or" (and deprecating &&/||).
[0] http://stackoverflow.com/questions/1426826/difference-betwee...