Loading feed…
Lobsters0 Hot0 comments3 min read
Keep if clauses side-effect free
Argues against writing if clauses that call methods with side effects, since the returned value's meaning is often ambiguous and the side-effecting call can be missed by a reader skimming code. Uses examples like enqueueMessage(), flushQueue(), and a real production example with Set.add() combined with continue and negation, showing how convoluted the logic becomes. Recommends always assigning the return value to a clearly named boolean or variable before testing it in the if statement, and avoiding short-circuit evaluation as a way to hide side-effecting calls.
Source: https://www.teamten.com/lawrence/programming/keep-if-clauses-side-effect-free.html. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
Recommended for you
Bình luận
Đang tải bình luận…
