-Wall ain't all
-Wall ain't all
25 comments
-
int unused_variable = 0;Dude wtf is your problem don’t just leave things lying about there don’t you know how to code I mean what the- I don’t go to your house and leave shit on the floor and just—
int _unused_variable = 0;Ok. We cool.
-
sometimes you need an unused variable. some uses in rust:
rs
// destructuring let (width, _height) = get_dimensions(); // trait implementations (i couldnt think of a better example for this) impl Into for AlwaysZero { fn into(_value: Self) -> { return 0; } } // some types (eg. Result) must be 'used' // assigned to a variable if we dont care about the return value let _ = returns_result("foo");
-
-
mfw my face when the go compiler fucking screams at me because I dared to declare a variable and not use it
-
IF THIS IS INTENTIONAL PUT AN UNDERSCORE BEFORE THE VARIABLE NAME YOU ABSOLUTE FUCKING MORON
-
didn’t know the go compiler’s name was steeve
-
-
"Don't worry too much about your loops bro, I am the apex of computer science research, I know every optimization in the book." Ok want to compile this? "Is that... An unused variable?!? WHAT THE FUCK ARE WE GOING TO DO GOD IS DEAD"
-
honestly my dumb ass will choose
for i in list:overfor i := range slice {every single time. I’m ugly and I’m proud!
-
-
-
I am guilty of passing Exception variables into try catches and not using them
-
undefined
catch(error) { // todo }
-
-
Function is changing a global variable, the global variable is checked after every call to the function. That's your return value.
-
I spent 3 hours debugging the serialization code to find out it the crash was because the function didn't have a return statement.
-
Sorry, cannot relate; Everything is a boolean when you're using JavaScript.
-
-
That's..... Terrible. Truly the stuff of nightmares!
-
OOP methods?
-
-
Idk, mb they expected you to modify smth passed by reference/pointer, and the compiler's too busy to care :)
-
Ok, you are certainly in one of those languages where plenty of your functions shouldn't return a value, and you won't ever let the compiler know that.
On all of the other languages, it's an error, not even a warning.
-
It's C++ and it just causes a SIGILL.
-
25 comments