in reply to Situation where warning "Found = in conditional, should be" seems obsolete

You need to fill up the character hopper on your keyboard so you can be more extravagant and expressive with your code. If this is code from a golf competition sure, do nasty stuff, but suck it up when things grump at you. If this is code for any other purpose take the time to write clear maintainable code.

And don't bother with the "time it takes to type" argument. In writing, reading and replying to this thread you have already used more time than you will ever save in keystroke time writing obfuscated code instead of maintainable code. Actually, you will save more time just in being able to understand what you wrote more quickly in the future (say, ten minutes from when you wrote it) than you lose by spending more time typing.

And in case you think that one complicated line is easier to understand than several shorter lines, especially where important stuff is at the end of the line, then you would be wrong because it isn't true despite what you might wish.

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond