On 4/6/22 00:04, arn...@skeeve.com wrote:
IMHO clear code beats saving a single branch
Sure, but clarity also argues for "&" over "&&" here. Writing "f(x) && f(y)" would incorrectly imply that it's important that f(y) should not be evaluated when f(x) is false, an implication that is incorrect here. Writing "f(x) & f(y)" tells the reader that both sides are safe to evaluate and that they can be evaluated in either order, something I found worth knowing when I read that part of the code.
