That doesn't test for equality, though.
An important semantic point. For example:
case 1..3
when 1..3: puts 'yay!'
else puts 'boo'
end
results in "boo", because (1..3) === (1..3) #=> false
Still, as the docs for Object#=== say:
"For class Object, effectively the same as calling #==, but typically
overridden by descendants to provide meaningful semantics in case
statements."
Numbers, strings, arrays, hashes, booleans...all these treat === as
==. I'm not arguing that they should be treated the same, or that we
should sweep the difference under the rug. I'm simply suggesting that
if you know the difference between #== and #===, particularly on the
objects that you place in your case statements, then under many
circumstances you can use a case statement as a convenience for
checking equality on many objects at once.
(Not that there was anything wrong with your initial suggestion of
Array#any?, of course.)
