Another comment in this post: >I've had the joy of seeing code which broke completely if you removed the line while(false){}. Some hideous synchronization bug

Another comment in this post: >I've had the joy of seeing code which broke completely if you removed the line while(false){}. Some hideous synchronization bug was solved by this line, and while it obviously wasn't the right solution, simply deleting it produced bad outputs. Profilers and processing tools are, as you say, other likely causes of dumb-looking code choices. https://news.ycombinator.com/item?id=10036050 https://news.ycombinator.com/item?id=10036050 I can also imagine methods with side-effects. The test is always false but a side-effect is necessary.