Correct use of && where only & makes sense
Shows up as a warning from Clang: use of logical '&&' with constant operand I wonder how many cases we have where && is used instead of & but with both operands non-constant, thus not causing any warning? Change-Id: I8fbbcf9c08f54f8803a08a4e8c54d7bd873af800
Showing
Please
register
or
sign in
to comment