Yep, variables that are merely declared are not initialized, so their value is not guaranteed. Could be anything.
Yep, variables that are merely declared are not initialized, so their value is not guaranteed. Could be anything.
You’re charging the class for a thought crime!!
Horrible code. First, it doesn’t compile because there’s no ;
at the end of the class definition.
And then more importantly you have a private destructor which means this CriminalScum’s destructor will never be called, so you can’t charge it with distruction either. Or are you telling me this CriminalScum has friends?
You gotta allocate your GFs statically or this just keeps happening.
Dude, imagine taking the time out of your day to actually make a meme (like the one posted). I really can’t be bothered.
As if it were so easy. You could already argue Facebook algos already facilitating genocides. Or radicalizing anti-vaxxers. And many others.
If an AI has gained the power to overthrow governments there’s no servers to unplug, because we probably rely so much on it that it’s similar to saying “unplug the internet” or “turn off all electricty”. Or frankly: “stop using oil”.
Yes, actually at my job a co-worker just found exactly such a bug yesterday: Debug build zeroed out the variable and the release build didn’t. So the bug only occurred in the release build, but could not be reproduced on the debug build where the developers work on. So in the end he found it because of the different compiler flags used for debug vs release builds at our work place.