@taradinoc @tom_forsyth @TheJare @vgebler Compilers shouldn't warn on things that you typed in exactly that have no other meaning.
-
-
Replying to @cmuratori
@taradinoc@tom_forsyth@TheJare@vgebler If I type while(0), there's nothing else that could possibly mean other than don't do that loop.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@tom_forsyth@TheJare@vgebler So the only thing the warning does is make me type something else. It does reduce the error rate.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@tom_forsyth@TheJare@vgebler If I'm blind or stupid, I'm just as likely to incorrectly type for(;;) as while(1), etc.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@tom_forsyth@TheJare@vgebler But any reasonable programmer never types while(1) or while(0) if they didn't mean it.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@tom_forsyth@TheJare@vgebler I disagree. Everyone makes typos.1 reply 0 retweets 0 likes -
Replying to @taradinoc
@taradinoc@tom_forsyth@TheJare@vgebler Well, speak for yourself then. I have literally never made either of those typos in 30 years.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@taradinoc@tom_forsyth@TheJare@vgebler It is certainly not giving me a warning _I_ can ever use.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@tom_forsyth@TheJare@vgebler If only there were a way for individuals/teams to disable specific warnings they found useless. ;)1 reply 0 retweets 0 likes -
Replying to @taradinoc
@taradinoc@tom_forsyth@TheJare@vgebler But that was the beginning of the discussion - Tom saying that you shouldn't disable any.1 reply 0 retweets 0 likes
@taradinoc @tom_forsyth @TheJare @vgebler I am arguing that you absolutely should disable some, because they are wastes of time.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.