Re:Google broke a conditional statement that verifies passwo...
by dataflow on Friday July 23, 2021 @01:45AM
(#27927608)
That has nothing to do with the standard though? The behavior is well-defined, it's just compilers warning about use of & tending to be error-prone (rightly or wrongly).
> What I would like to write in unit tests:
> ok &= check(x);
> That gets you angry messages from static analysis