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:
// 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: over for 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
catch(error) {
// todo
}laughs in golang
I would love to use golang for this but it’s standard library alone is bigger than the amount of available RAM.
Interesting, since golang only includes the parts of the stdlib that are used in the executable binary.
I just tested it and a simple hello world program still produces a 1.7MiB binary, while the device only has 512KiB of RAM.
package main
import "fmt"
func main() {
fmt.Println("hello world")
}
Strip the debug info, should be a lot smaller. Also check out TinyGo, it's meant for embedded devices
BTW: what are you using instead to get small binaries/scripts?
I'm currently using C++
Likely your C++ implementation also doesn't ship the full standard library. And you may even turn off exceptions and RTTI.
Function is changing a global variable, the global variable is checked after every call to the function. That's your return value.
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.
Post funny things about programming here! (Or just rant about your favourite programming language.)