stupid places meaning "the actual scope they're needed in instead of a whole function for no reason"?
-
-
Replying to @chaosprime
could have it's uses: e.g. put same var name in two sub-blocks of the same function to create heisenbugs and gaslight QA team.
1 reply 0 retweets 2 likes -
-
Replying to @chaosprime
I'm just "thinking like an attacker". Everyone knows I'm pure as driven and would never do such things.
1 reply 0 retweets 1 like -
Replying to @ColumPaget
yeah i'm sure your hat is just that color because it got smudged from bumping against your halo
2 replies 0 retweets 0 likes -
Replying to @chaosprime
but, seriously, what *ARE* the civilian applications?
1 reply 0 retweets 0 likes -
Replying to @ColumPaget
if(condition) { int some_damn_thing_i_only_care_about_in_this_case = expensive(); do_thing(…); } else { whatevs(); }
2 replies 0 retweets 0 likes -
Replying to @chaosprime
and I'm only thinking the bits are saved because I'm thinking the stack might be modified, which I suspect it isn't
1 reply 0 retweets 0 likes -
Replying to @ColumPaget
yeah i dunno, deeper compiler shit than i tend to worry about
1 reply 0 retweets 0 likes -
Replying to @chaosprime
I suspect it's going to differ from compiler to compiler too.
1 reply 0 retweets 0 likes
one is forced to suspect
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.